Triple
T16949111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interagency Language Roundtable scale |
E411138
|
entity |
| Predicate | level1Label |
P21560
|
FINISHED |
| Object | Elementary proficiency |
—
|
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: Elementary proficiency | Statement: [Interagency Language Roundtable scale, level1Label, Elementary proficiency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: level1Label Context triple: [Interagency Language Roundtable scale, level1Label, Elementary proficiency]
-
A.
level1Feature
Indicates that one entity possesses or is associated with a primary or first-tier feature of another entity.
-
B.
levelIDescription
Indicates that an entity provides a textual description of its difficulty or progression level.
-
C.
levels
Indicates that one entity adjusts, equalizes, or smooths out the height, intensity, or degree of another entity.
-
D.
levelServed
Indicates that a particular service, function, or resource is provided or made available at a specified level or tier.
-
E.
labelOf
chosen
Indicates that one entity serves as the name, tag, or identifying label assigned to another entity.
- 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.