Triple
T1607386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 285 |
E34535
|
entity |
| Predicate | isMajorTruckRoute |
P19599
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Interstate 285, isMajorTruckRoute, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorTruckRoute Context triple: [Interstate 285, isMajorTruckRoute, yes]
-
A.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
B.
isMajorInterchangeFor
Indicates that one location functions as a primary hub where multiple routes or lines connect or transfer between each other for another location.
-
C.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
-
D.
isMajorArterialFor
Indicates that something functions as a primary high-capacity route or conduit serving as a main channel for movement, flow, or traffic for something else.
-
E.
hasTruckTraffic
chosen
Indicates that there is truck-related vehicular movement or flow occurring on or through a specified location or route.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fa6926081908bc78d15c0be3185 |
completed | March 5, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69a907c35f848190a2428c52e81d013e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.