Triple
T7522444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri and Illinois |
E177804
|
entity |
| Predicate | shareInterstateHighway |
P16566
|
FINISHED |
| Object | Interstate 55 |
—
|
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 55 | Statement: [Missouri and Illinois, shareInterstateHighway, Interstate 55]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareInterstateHighway Context triple: [Missouri and Illinois, shareInterstateHighway, Interstate 55]
-
A.
isIntercityHighway
Indicates that a given road segment functions as a highway connecting different cities or urban areas.
-
B.
stateHighwayServedBy
Indicates that a particular state highway is provided service or coverage by a specified transportation route, agency, or facility.
-
C.
nearestInterstateHighway
Indicates that one interstate highway is the closest in distance to a given location or route compared to all other interstate highways.
-
D.
isFreeway
Indicates that a given road segment functions as a freeway, typically designed for high-speed, limited-access vehicular traffic.
-
E.
hasInterstate
chosen
Indicates that there exists an interstate connection or highway link between the related entities.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f7c3c4c08190ad418978afcc98ec |
completed | March 27, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:46 p.m.