Triple
T24375343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MARTA East Line nearby |
E614456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | MARTA rail corridor segment |
C48396
|
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: MARTA rail corridor segment Context triple: [MARTA East Line nearby, instanceOf, MARTA rail corridor segment]
-
A.
MARTA rail line
A MARTA rail line is a rapid transit route within the Metropolitan Atlanta Rapid Transit Authority system that provides high-frequency passenger train service between key destinations across the Atlanta metropolitan area.
-
B.
MARTA rail station
A MARTA rail station is a designated facility along the Metropolitan Atlanta Rapid Transit Authority’s rail network where passengers access, board, and transfer between trains and related transit services.
-
C.
AeroTrain station
An AeroTrain station is a designated facility where passengers board, disembark, and transfer between AeroTrains, providing platforms, ticketing, waiting areas, and related services for high-speed or automated airport rail transit.
-
D.
MARC station
A MARC station is a designated passenger rail stop along the Maryland Area Regional Commuter (MARC) train network, providing boarding, alighting, and related services for regional commuters.
-
E.
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.
- F. None of above. chosen
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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:02 a.m.