Triple
T5237405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Credit and Qualifications Framework |
E118256
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | qualifications framework |
C15891
|
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: qualifications framework Context triple: [Scottish Credit and Qualifications Framework, instanceOf, qualifications framework]
-
A.
qualification framework
chosen
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.
-
B.
engineering qualification
An engineering qualification is a formal credential or certification that verifies an individual's technical knowledge, skills, and competence to practice in a specific engineering discipline.
-
C.
education policy framework
An education policy framework is a structured set of principles, goals, and guidelines that shapes how educational systems are organized, governed, funded, and evaluated to achieve desired learning and equity outcomes.
-
D.
secondary school qualification
A secondary school qualification is an official credential awarded upon successful completion of upper-level schooling, typically certifying readiness for higher education, vocational training, or entry into the workforce.
-
E.
regulatory framework
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:49 p.m.