Triple
T12945390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buffalo Main Light Rail line on Main Street |
E309748
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | surface-running transit corridor |
C2488
|
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: surface-running transit corridor Context triple: [Buffalo Main Light Rail line on Main Street, instanceOf, surface-running transit corridor]
-
A.
planned transit corridor
A planned transit corridor is a designated route or area reserved for future development of public transportation infrastructure, such as bus rapid transit or rail lines, to guide growth and improve regional mobility.
-
B.
underground rail corridor
An underground rail corridor is a subsurface passageway engineered to safely guide trains between stations, housing tracks, utilities, and supporting infrastructure while minimizing surface disruption.
-
C.
rapid transit line segment
chosen
A rapid transit line segment is a contiguous portion of a rapid transit route between two defined points (such as stations, junctions, or terminals) that carries high-frequency, high-capacity passenger rail service.
-
D.
suburban railway corridor
A suburban railway corridor is a dedicated rail route connecting city centers with surrounding residential suburbs, designed to support frequent, high-capacity commuter train services.
-
E.
transport corridor
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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:43 p.m.