Triple
T29216424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington, D.C.–Chicago route |
E740678
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intercity passenger rail corridor |
C2952
|
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: intercity passenger rail corridor Context triple: [Washington, D.C.–Chicago route, instanceOf, intercity passenger rail corridor]
-
A.
intercity passenger rail project
An intercity passenger rail project is a coordinated planning, design, and construction effort to develop or improve rail infrastructure and services that transport people efficiently between cities over medium to long distances.
-
B.
freight rail corridor
A freight rail corridor is a designated railway route primarily used for the efficient, high-capacity movement of goods and cargo between industrial, commercial, and logistics hubs.
-
C.
passenger rail service
Passenger rail service is a transportation system that operates trains to carry people between locations on a scheduled basis, typically offering various classes of comfort and amenities.
-
D.
commuter rail line
A commuter rail line is a passenger train service that operates on fixed tracks and schedules to connect suburban or outlying areas with a central city, primarily serving daily work and school commuters.
-
E.
transport corridor
chosen
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 12:13 p.m.