Triple
T33965976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorado State Highway 62 |
E870852
|
entity |
| Predicate | connectedHighwayAtEasternTerminus |
P22217
|
FINISHED |
| Object | U.S. Route 550 |
—
|
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: U.S. Route 550 | Statement: [Colorado State Highway 62, connectedHighwayAtEasternTerminus, U.S. Route 550]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedHighwayAtEasternTerminus Context triple: [Colorado State Highway 62, connectedHighwayAtEasternTerminus, U.S. Route 550]
-
A.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
B.
easternTerminusLocatedOn
Indicates that the eastern endpoint of a route, line, or path is situated on or at a specified feature or location.
-
C.
roadTerminusOf
chosen
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
D.
expresswayServedBy
Indicates that a particular expressway is provided with service or access by a specified facility, route, or service entity.
-
E.
motorwayConnectionWith
Indicates that two locations are directly connected by a motorway, allowing vehicular travel between them via that road.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 1, 2026, 1:50 a.m.