Triple
T16949096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interagency Language Roundtable scale |
E411138
|
entity |
| Predicate | hasLevelRange |
P99406
|
FINISHED |
| Object | 0–5 |
—
|
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: 0–5 | Statement: [Interagency Language Roundtable scale, hasLevelRange, 0–5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevelRange Context triple: [Interagency Language Roundtable scale, hasLevelRange, 0–5]
-
A.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
B.
yLevelRange
Indicates that one entity’s vertical position or height falls within a specified range relative to another entity or reference level.
-
C.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
D.
hasLevelNumber
chosen
Indicates that an entity is associated with a specific level identified by a numerical value.
-
E.
hasLevelType
Indicates that an entity is associated with a specific type or category of level (e.g., difficulty, hierarchy, or stage).
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb4b1b08190b608d36a209ed6bd |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.