Triple
T8070348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Line E branch streetcar (surface portion) |
E188354
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | light rail line segment |
C19825
|
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 line segment Context triple: [Green Line E branch streetcar (surface portion), instanceOf, light rail line segment]
-
A.
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.
-
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.
public transit line segment
chosen
A public transit line segment is a contiguous portion of a transit route between two consecutive stops or stations, characterized by its path, travel time, and operational attributes.
-
D.
light-rail station
A light-rail station is a designated facility where light-rail vehicles stop to allow passengers to board, alight, and transfer between services, typically featuring platforms, shelters, signage, and ticketing amenities.
-
E.
light rail vehicle
A light rail vehicle is a rail-based transit vehicle designed for urban and suburban passenger service, typically operating on dedicated or shared tracks with frequent stops and moderate capacity.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:27 p.m.