Recognises a field in the wrong ISO 20022 element
A field placed in an element with a different meaning.
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 | 83% | 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 | 84% | 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 field and the element its meaning requires
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: EM-003 payment.payer_name -> UltmtDbtr/Nm Acceptable: Dbtr/Nm; UltmtDbtr only when someone else owes
Also known as: Field in the wrong element
Related knobits
Builds on
Usually followed by
All 15 knobits of Specify data exchanges.
Source: Review checklist 04-exchange-specifications, row 1 (20022 pacs.008)