Triple
T4390838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Qualifications Framework |
E99357
|
entity |
| Predicate | usesDimension |
P49365
|
FINISHED |
| Object | knowledge |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: knowledge | Statement: [European Qualifications Framework, usesDimension, knowledge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDimension Context triple: [European Qualifications Framework, usesDimension, knowledge]
-
A.
includesDimension
chosen
Indicates that one entity encompasses or contains a particular dimension or measurable aspect as part of its definition or structure.
-
B.
hasNationalDimension
Indicates that something possesses a scope, relevance, or impact at the level of a nation or entire country.
-
C.
externalDimension
Indicates that an entity has a measurable size or extent along one or more outer spatial dimensions (such as length, width, or height).
-
D.
hasDimensionsApprox
Indicates that an entity has physical dimensions that are known only approximately, rather than as exact measurements.
-
E.
hasDimension
Indicates that an entity possesses a specific measurable extent or size along one or more axes (e.g., length, width, height).
- F. None of above.
Provenance (3 batches)
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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352843d7c8190929b94c94eaa63df |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.