Recognises conflicting retention periods with no precedence
Two bases for one class with different periods and no rule between them.
Can AI do this?
Not settled yet The benchmark tested this, but the models' answers do not settle yet whether they master it. 0 of 4 models in the current benchmark master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 84% | Not shown |
| gemini-3.5-flash-lite | Low cost | 84% | Not shown |
| gpt-6-luna | Low cost | 83% | Not shown |
| claude-haiku-5-5 | Low cost | 83% | Not shown |
Mastered means a probability of at least 90% that the model has this knobit, estimated from its graded answers. “Not shown” means the answers do not settle it either way. How the models are tested.
What it looks like in practice
Expected result: The bases and the precedence to decide
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: RR-004 advice recordings: MiFID II 5 years and a national rule 7 years Acceptable: Longer period applied, or a ruling recorded
Also known as: Conflicting periods with no precedence
Related knobits
Builds on
Usually followed by
All 17 knobits of Set the retention and disposition schedule.
Source: Review checklist 02-retention-schedule, row 3 (MiFID; DMBOK)