Triple
T35130918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common European Framework of Reference for Languages |
E1014432
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | language proficiency framework |
C38299
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: language proficiency framework Context triple: [Common European Framework of Reference for Languages, instanceOf, language proficiency framework]
-
A.
language proficiency scale
chosen
A language proficiency scale is a structured framework that categorizes and describes a learner’s ability to understand, speak, read, and write a language across progressive levels of competence.
-
B.
language proficiency assessment
A language proficiency assessment is a systematic evaluation tool designed to measure an individual's ability to understand, speak, read, and write in a specific language across defined competency levels.
-
C.
language qualification
A language qualification is a formal certification or credential that verifies an individual's proficiency level in a specific language according to recognized standards.
-
D.
qualification framework
A qualification framework is a structured system that defines and organizes levels of learning achievements, skills, and competencies to ensure comparability, transparency, and recognition of qualifications across contexts.
-
E.
educational framework
An educational framework is a structured model that outlines the principles, goals, content, methods, and assessment strategies guiding the design and delivery of teaching and learning experiences.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.