Triple
T10637722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Line trunk subway |
E250636
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | underground light rail corridor |
C21697
|
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: underground light rail corridor Context triple: [Green Line trunk subway, instanceOf, underground light rail corridor]
-
A.
underground rail corridor
chosen
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.
-
B.
light rail transit line
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.
-
C.
urban rail loop line
An urban rail loop line is a circular or near-circular transit route within a city that connects multiple districts and intersecting lines, allowing continuous, bidirectional travel without a terminal endpoint.
-
D.
monorail transit line
A monorail transit line is an elevated or ground-level guided transportation system in which trains run on a single rail, typically used for urban or campus passenger service.
-
E.
diesel light rail line
A diesel light rail line is a passenger rail transit system that operates lighter, typically more frequent trains powered by diesel engines on dedicated or shared tracks, serving urban or regional 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:04 p.m.