Triple
T5006491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansas Turnpike (shared alignment near Topeka) |
E112506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tolled highway segment |
C3789
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: tolled highway segment Context triple: [Kansas Turnpike (shared alignment near Topeka), instanceOf, tolled highway segment]
-
A.
toll highway
A toll highway is a high-speed road where drivers must pay a fee, typically at toll booths or electronically, to use the roadway for travel.
-
B.
highway segment
A highway segment is a continuous portion of a highway between two defined endpoints, such as interchanges, intersections, or mile markers, characterized by consistent physical and operational attributes.
-
C.
toll road
chosen
A toll road is a roadway for which drivers must pay a fee, typically at designated points or electronically, to use its infrastructure.
-
D.
high-occupancy toll lanes
High-occupancy toll lanes are special highway lanes that allow vehicles with multiple occupants to travel for free or at reduced cost while single-occupant vehicles can use them by paying a variable toll designed to manage congestion and maintain faster traffic flow.
-
E.
road segment
A road segment is a continuous portion of a roadway between two defined endpoints, such as intersections or junctions, characterized by uniform attributes like direction, number of lanes, and speed limit.
- F. None of above.
Provenance (1 batch)
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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:35 p.m.