Triple
T34801083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRT Jerome Avenue elevated segment |
E1003219
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | elevated railway segment |
C539
|
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: elevated railway segment Context triple: [IRT Jerome Avenue elevated segment, instanceOf, elevated railway segment]
-
A.
elevated railway
chosen
An elevated railway is a rail transport system in which tracks and stations are built on raised structures above ground level, typically supported by columns or girders, to avoid interference with street traffic.
-
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.
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.
-
D.
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.
-
E.
suburban railway branch
A suburban railway branch is a secondary rail line that diverges from a main route to serve residential and commuter areas on the outskirts of a city.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.