Triple
T28997660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Line Atlantic station |
E736210
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | at-grade light rail station |
C37096
|
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: at-grade light rail station Context triple: [Gold Line Atlantic station, instanceOf, at-grade light rail station]
-
A.
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.
-
B.
at-grade station
chosen
An at-grade station is a railway or transit station where the platforms and tracks are located at ground level, typically intersecting with surrounding roads and pedestrian pathways on the same plane.
-
C.
rapid transit station
A rapid transit station is a designated facility where passengers board, alight, and transfer between high-frequency urban rail or metro services, typically featuring platforms, ticketing areas, and access to surrounding streets or other transport modes.
-
D.
commuter rail station
A commuter rail station is a designated facility where passengers board and alight regional trains that connect suburbs or outlying areas with urban centers, typically offering platforms, ticketing, and basic passenger amenities.
-
E.
DART Light Rail station
A DART Light Rail station is a designated passenger facility along Dallas Area Rapid Transit’s light rail network where riders can board, alight, and transfer between trains and connecting transit services.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 9:32 a.m.