Triple
T2483388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Aurora and Elgin Railroad |
E55870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interurban electric railway |
C5215
|
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 railway Context triple: [Chicago Aurora and Elgin Railroad, instanceOf, interurban electric railway]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
light rail transit line
chosen
A light rail transit line is a fixed-route urban or suburban rail corridor using electrically powered, relatively low-capacity trains that operate on dedicated or semi-exclusive tracks to provide frequent, short- to medium-distance passenger service.
-
E.
rail transit
Rail transit is a public transportation system that moves passengers or freight along fixed steel tracks using trains, subways, trams, or light rail vehicles, typically in urban or intercity corridors.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:45 p.m.