Recognises a regulatory return input missing from the critical data elements
An input of a regulatory return that is not on the CDE list.
Can AI do this?
People still lead Few or none of the tested AI models showed they master this. 0 of 4 models in the current benchmark master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 74% | Not shown |
| gemini-3.5-flash-lite | Low cost | 2% | Not mastered |
| gpt-6-luna | Low cost | 72% | Not shown |
| claude-haiku-5-5 | Low cost | 74% | 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: A CDE for the input, with its owner
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: RP-31 DGS single customer view reads party.personal_code (PE-202); no CDE Acceptable: CD for PE-202, owner Customer data owner
Also known as: Regulatory report input not a CDE
Related knobits
Builds on
- Q-151 Explains selecting critical data elements from their uses
- Q-152 Explains the BCBS 239 principles for risk data
All 10 knobits of Select the critical data elements.
Source: Review checklist 01-cdes, row 2 (BCBS 239 P3, P4)