When a statement is incorrect, it will tend to follow a certain pattern. Change out the subject words and you get the same pattern. For instance, hasty generalization:
All bleeps are bloops.
All gerbils are purple.
All Asians are smart.
These are all false reasoning, the falseness is inherent to the sentence structure such that if we change out “bleeps” and “bloops” for any other subject, it’s still hasty generalization. If we were to build a piece of software that allows users to flag a statement for review, the reviewer could be given the statement with different subject words. For instance, if someone argues a piece of obvious bad reasoning like “All black people are bad.” the reviewer might be given “All oranges are bad.” Without race to potentially trigger the reviewer’s bias, the reviewer can plainly see that the sentence is a hasty generalization. This will help prevent bias and politics from interfering with the rational review of statements.
If that’s not found to be good enough alone, we could use it as part of a larger strategy.
If the difference between a hasty generalization and a fact is that the fact is true, then to call something a hasty generalization we need to say something about its factualness.
Not all claims of the form “all Xs are Ys” are false, and neither is every conclusion of the form “all Xs are Ys” a product of bad reasoning. Suppose your software were to replace “All electrons are negatively charged” with “All rabbits are highly educated”. How is the reviewer supposed to react? Is she supposed to conclude that the original statement is false? Why?
You are using the phrase “hasty generalization” in a highly non-standard way here. Philosophers classify hasty generalization as an informal fallacy. The “informal” means that the content matters, not just the formal structure of the argument. Also, a hasty generalization is an argument, not a single sentence. An example of a hasty generalization would be, “I was cut off by an Inuit driver on the way to work today. All Inuits must be terrible drivers.” The fallacy is that the evidence being appealed to (being cut off by one Inuit driver) involves much too small a sample for a reliable generalization to an entire population. But just looking at the formal structure of the argument isn’t going to tell you this.
There are formal fallacies, where the fallacy in the reasoning is subject-independent. An example would be “affirming the consequent”—arguing that since B is true and A implies B, A must also be true. You could build the kind of software you envisage for formal fallacies, but you’d need another strategy for catching and dealing with informal fallacies.
Sorting opinion and fact with code:
When a statement is incorrect, it will tend to follow a certain pattern. Change out the subject words and you get the same pattern. For instance, hasty generalization:
All bleeps are bloops. All gerbils are purple. All Asians are smart.
These are all false reasoning, the falseness is inherent to the sentence structure such that if we change out “bleeps” and “bloops” for any other subject, it’s still hasty generalization. If we were to build a piece of software that allows users to flag a statement for review, the reviewer could be given the statement with different subject words. For instance, if someone argues a piece of obvious bad reasoning like “All black people are bad.” the reviewer might be given “All oranges are bad.” Without race to potentially trigger the reviewer’s bias, the reviewer can plainly see that the sentence is a hasty generalization. This will help prevent bias and politics from interfering with the rational review of statements.
If that’s not found to be good enough alone, we could use it as part of a larger strategy.
Every square is a rhombus
If the difference between a hasty generalization and a fact is that the fact is true, then to call something a hasty generalization we need to say something about its factualness.
Not all claims of the form “all Xs are Ys” are false, and neither is every conclusion of the form “all Xs are Ys” a product of bad reasoning. Suppose your software were to replace “All electrons are negatively charged” with “All rabbits are highly educated”. How is the reviewer supposed to react? Is she supposed to conclude that the original statement is false? Why?
You are using the phrase “hasty generalization” in a highly non-standard way here. Philosophers classify hasty generalization as an informal fallacy. The “informal” means that the content matters, not just the formal structure of the argument. Also, a hasty generalization is an argument, not a single sentence. An example of a hasty generalization would be, “I was cut off by an Inuit driver on the way to work today. All Inuits must be terrible drivers.” The fallacy is that the evidence being appealed to (being cut off by one Inuit driver) involves much too small a sample for a reliable generalization to an entire population. But just looking at the formal structure of the argument isn’t going to tell you this.
There are formal fallacies, where the fallacy in the reasoning is subject-independent. An example would be “affirming the consequent”—arguing that since B is true and A implies B, A must also be true. You could build the kind of software you envisage for formal fallacies, but you’d need another strategy for catching and dealing with informal fallacies.