CK-25 Error taxonomy and error analysis (failure mode analysis; confusion analysis)
Classify reviewed failures into defined types such as invented fact, wrong attribution, omission, wrong scope and arithmetic, and produce error counts by type.
What it does
Classifies reviewed failures into defined types, such as invented fact, wrong attribution, omission, wrong scope and arithmetic, and counts them. Artefact: error counts by type. Read which types dominate, and change prompts, checks or review focus.
When to use it
Use when a pilot or review has found errors and you need to know which kinds dominate so you can change prompts, checks or review focus.
When it does not fit
Use after any pilot. Misfit: overlapping types, so counts do not add.
Result format
The result is a table of error counts by defined type, such as invented fact, wrong attribution, omission, wrong scope and arithmetic, with the failed items listed under each type. It names the types that dominate and says what change to prompts, checks or review focus follows.
Requirements on the material
| Property | Requirement type | Requirement |
|---|---|---|
| Content type | Always applies | requires=text |
| Unit of analysis | Always applies | requires=claim; requires=record |
| Appraises source credibility | Applies in some cases | no |
Not restricted on: Structure, Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.
| Minimum material | a set of reviewed failures, usually 30 or more |
|---|---|
| Additional sources needed | none |
| Not for (rules) | none |
| Not for (text) | Wrong choice when error types overlap, so that counts do not add up. Types must be defined before counting. |
Choosing and ordering
| Kind of technique | Verification technique, runs in step 6 |
|---|---|
| Phase tag | validate |
| Other phase tags | analyse |
| Kind of finding | pattern; risk |
| Question answered | why; what next |
| Strongest statement it supports | describe |
| Needs as input |
|
| Makes as output |
|
| Must exist first | None |
| Loop target | return to analyse |
Library checks by stakes
Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: judgement dependent.
| Stakes | Check | Person involved | Counts as a different method |
|---|---|---|---|
| exploratory | spot check | optional | no |
| decision-informing | spot check | optional | no |
| decision-informing | human review sample | needed; left out below high stakes | no |
| high-stakes | spot check | optional | no |
| high-stakes | human review sample | needed | no |
| high-stakes | independent review | needed | no |
| high-stakes | assumption and limitation statement | none | no |
Failure modes and limits
| Model suitability | human judgement required |
|---|---|
| Typical model failure | Assigns tidy categories to errors it has not examined. |
| Error sources | input data; coder or rater judgement |
| Certainty limits | Certainty drops when types overlap (indirectness), when few failures were reviewed (imprecision) and when one reviewer classified them (risk of bias). |
Related techniques
- should follow CK-24 Review sampling design (random audit sample; stratified sample; risk-based sampling; acceptance sampling; rule of three): the sampled and reviewed items supply the failures
- should follow CK-26 Independent human review of model output (expert review; adjudication; human oversight): reviewer decisions supply the failures
- pairs with CK-27 Adversarial testing of an extraction pipeline (red-teaming; chaos testing): adversarial failures can be classified with the same taxonomy
Evidence and tag basis
Documented. Large-scale human evaluation found substantial hallucinated content in all neural summarisers tested (2020). An eight-type leakage taxonomy from another field is a worked example. (Maynez et al. 2020, ACL; Kapoor and Narayanan 2022, arXiv 2207.07048)
Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.