Explains how a metamodel is populated from metadata sources
Every class realises metadata a use case needs, and every class and relationship names the source that fills it; a relationship no source can populate promises an answer the catalogue will never have.
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 | 96% | Not shown |
| gemini-3.5-flash-lite | Low cost | 20% | Not shown |
| gpt-6-luna | Low cost | 86% | Not shown |
| claude-haiku-5-5 | Low cost | 96% | 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: Every class realises metadata a use case needs, and every class and relationship names the source that fills it; a relationship no source can populate promises an answer the catalogue will never have.
How it is assessed: Answers a written question on the metamodel population correctly
Related knobits
Builds on
- M-251 Explains metamodel layers, classes and relationships
- M-151 Explains use-case-driven metadata requirements
Needed for
- M-203 Recognises a metamodel relationship no source can populate
- M-206 Recognises a metamodel class serving no use case
All 12 knobits of Design the metamodel.
Source: Practice the stage 2 reference and review checklist rest on