Triple
T13386957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stevenson Expressway (I-55) access nearby |
E319468
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | highway access point cluster |
C32940
|
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: highway access point cluster Context triple: [Stevenson Expressway (I-55) access nearby, instanceOf, highway access point cluster]
-
A.
highway approach route
A highway approach route is a roadway segment or path that guides vehicles from local or arterial roads onto a highway, facilitating safe and efficient merging into higher-speed traffic.
-
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.
motorway service area
A motorway service area is a designated roadside facility along a motorway that provides drivers and passengers with services such as fuel, food, restrooms, parking, and rest areas.
-
D.
controlled-access highway
A controlled-access highway is a high-speed road designed for uninterrupted traffic flow, featuring limited entry and exit points via ramps, no at-grade intersections, and restrictions on pedestrian and non-motorized access.
-
E.
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.
- F. None of above. chosen
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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:34 p.m.