Recognises value date and booking date confused
A mapping fills one date with the other.
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 | 80% | Not shown |
| gemini-3.5-flash-lite | Low cost | 70% | Not shown |
| gpt-6-luna | Low cost | 80% | Not shown |
| claude-haiku-5-5 | Low cost | 80% | 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 mapping and the right source date
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: MP-005 payment.value_date <- SR-003 BookgDt Acceptable: ValDt for value date, BookgDt for booking date
Also known as: Value date and booking date confused
Related knobits
Builds on
All 18 knobits of Map sources to targets.
Source: Review checklist 02-source-to-target-mapping, row 3 (20022 camt.053; DMBOK)