Triple
T11698700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago South Shore and South Bend Railroad |
E278064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interurban electric railroad |
C17649
|
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: interurban electric railroad Context triple: [Chicago South Shore and South Bend Railroad, instanceOf, interurban electric railroad]
-
A.
interurban railroad
chosen
An interurban railroad is an electric railway system that provides passenger and sometimes freight service between cities and towns, typically operating on dedicated tracks or street-running routes over medium distances.
-
B.
suburban commuter train
A suburban commuter train is a passenger rail service designed to transport people efficiently between residential suburbs and urban centers, typically operating on fixed schedules with frequent stops during peak travel times.
-
C.
elevated railway
An elevated railway is a rail transport system in which tracks and stations are built on raised structures above ground level, typically supported by columns or girders, to avoid interference with street traffic.
-
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.
rapid transit line
A rapid transit line is a high-capacity, high-frequency urban rail route operating on an exclusive or mostly separated right-of-way to provide fast, reliable public transportation between key areas of a city or metropolitan region.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:40 p.m.