Triple
T8162399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 184 (Idaho) |
E190605
|
entity |
| Predicate | systemDesignation |
P81036
|
FINISHED |
| Object | Interstate 184 |
—
|
NE NERFINISHED |
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: Interstate 184 | Statement: [Interstate 184 (Idaho), systemDesignation, Interstate 184]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemDesignation Context triple: [Interstate 184 (Idaho), systemDesignation, Interstate 184]
-
A.
missionDesignationSystem
Indicates a system that assigns or manages official designations or identifiers for missions.
-
B.
designatorType
Indicates the specific role or category of a designator used to identify or reference an entity within a system or context.
-
C.
prototypeDesignation
Indicates that one entity is designated or identified as a prototype version or exemplar of another entity.
-
D.
exampleDesignation
Indicates that one entity is identified or labeled as a representative or illustrative instance of another entity.
-
E.
hasInternalDesignationFor
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
- F. None of above. chosen
Provenance (4 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_69ca82c0ef14819083713f4473dd847c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4556b45c819089eb15ad027b036a |
completed | March 31, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb40a017608190b6b48cf60335fa8d |
completed | March 31, 2026, 3:33 a.m. |
Created at: March 30, 2026, 5:38 p.m.