Triple
T34611169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 71–U.S. Route 36 interchange vicinity |
E888740
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation infrastructure area |
C2978
|
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: transportation infrastructure area Context triple: [Interstate 71–U.S. Route 36 interchange vicinity, instanceOf, transportation infrastructure area]
-
A.
transport infrastructure network
A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
-
B.
road infrastructure
chosen
Road infrastructure encompasses the physical structures, systems, and facilities—such as roads, bridges, tunnels, signage, and drainage—designed and built to support safe and efficient vehicular and pedestrian transportation.
-
C.
public transportation infrastructure
Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
-
D.
transport infrastructure name
A transport infrastructure name identifies a specific facility or network element used for the movement of people or goods, such as a road, railway line, airport, or port.
-
E.
road transportation corridor
A road transportation corridor is a designated linear area of land that accommodates one or more roadways and associated infrastructure to enable the efficient movement of vehicles, goods, and people between key origins and destinations.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.