Triple
T16949098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interagency Language Roundtable scale |
E411138
|
entity |
| Predicate | maximumLevel |
P29667
|
FINISHED |
| Object | 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: 5 | Statement: [Interagency Language Roundtable scale, maximumLevel, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumLevel Context triple: [Interagency Language Roundtable scale, maximumLevel, 5]
-
A.
maximumCeiling
Indicates the highest allowable or achievable limit or value that something cannot exceed.
-
B.
minimumLevel
Indicates that one entity specifies the lowest allowable or required level, degree, or threshold at which another entity, condition, or action becomes valid or applicable.
-
C.
maximumNumber
chosen
Indicates that one entity specifies the highest allowable or observed quantity, value, or count associated with another entity.
-
D.
maximumDepth
Indicates the greatest extent or deepest level reached by something within a given context or structure.
-
E.
finalLevelType
Indicates the type or category assigned to the final level or stage of a process, system, or hierarchy.
- 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.