Triple
T29821649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenmore subway |
E757259
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | underground rail segment |
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: underground rail segment Context triple: [Kenmore subway, instanceOf, underground rail segment]
-
A.
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.
-
B.
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.
-
C.
subway line
A subway line is a fixed route within an urban rail transit system, consisting of a sequence of stations and tracks over which trains operate according to a scheduled service.
-
D.
MARTA rail corridor segment
A MARTA rail corridor segment is a defined portion of the Metropolitan Atlanta Rapid Transit Authority’s rail network, representing a continuous stretch of track and associated infrastructure between two operationally significant points.
-
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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:29 p.m.