Bibliographic record
Abstract
In his book on fallacies, Hamblin (1970) built a simple system for argumentation in dialogue he called the Why-Because System with Questions. In his discussion of this system, he replaced the concept of burden of proof with a simpler concept of initiative, which could be described as something like getting the upper hand as the argumentation moves back and forth in the dialogue between the one party and the other. No doubt he realized that the concept of burden of proof was too complex a matter to be dealt with in the limited scope of his chapter on formal dialogue systems. In this chapter, it is shown how an extended version of Hamblin’s dialogue system provides a nice way of modeling the phenomenon of shifting of burden of proof in a dialogue, yielding with a precise way of distinguishing between different kinds of burden of proof, and dealing with fallacies like the argumentum ad ignorantiam (argument from negative evidence). Over forty years has passed since the publication of Hamblin’s book Fallacies (1970), and there has been much written on the subject of argumentation since that time. One might think that such a book would have long ago ceased to have much value in contributing to the latest research. Such is not the case, however, especially with regard to Hamblin’s remarkably innovative Chapter 8 on formal dialogue systems, a chapter that provided the basis for much subsequent work. To give an example of a formal dialogue system of the kind he recommended in Chapter 8, he built a Why-Because System with Questions. A leading feature of this system is that it has a speech act representing a move in a dialogue in which one party asks the other party to prove, or give an argument to support a claim made by the first party. The Hamblin system has several rules for managing dialogues in which such support request questions are asked, and need to be responded to. It is shown in Chapter 5 how these rules are fundamentally important in attempting to build any formal dialogue system designed to be a framework modeling the operation of burden of proof in rational argumentation.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.008 | 0.019 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.004 | 0.016 |
| Scholarly communication | 0.010 | 0.021 |
| Open science | 0.002 | 0.006 |
| Research integrity | 0.004 | 0.007 |
| Insufficient payload (model declined to judge) | 0.011 | 0.003 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".