Triple
T25608886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest Baltimore Metro corridor |
E641988
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transportation 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: public transportation corridor Context triple: [Northwest Baltimore Metro corridor, instanceOf, public transportation corridor]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 4:40 p.m.