Triple
T22808540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Line B branch |
E564604
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | light rail service branch |
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: light rail service branch Context triple: [Green Line B branch, instanceOf, light rail service branch]
-
A.
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.
-
B.
rapid transit line segment
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.
-
C.
light metro
A light metro is a grade-separated, medium-capacity urban rail transit system that uses smaller trains and shorter headways than full-scale metros to efficiently serve moderate-demand corridors.
-
D.
light rail expansion project
A light rail expansion project is a coordinated planning, design, and construction effort to extend an existing light rail transit system’s routes, capacity, and supporting infrastructure to serve additional areas and riders.
-
E.
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.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:32 p.m.