Triple
T5315786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government Center Metrorail station |
E119143
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Metrorail station |
C463
|
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: Metrorail station Context triple: [Government Center Metrorail station, instanceOf, Metrorail station]
-
A.
rapid transit station
chosen
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.
-
B.
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.
-
C.
monorail station
A monorail station is a designated facility where passengers board, alight, and transfer to monorail trains, typically featuring elevated platforms, access structures, and passenger amenities.
-
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.
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.
- 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_69bd446b57bc8190a513d2e6c40314f3 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:54 p.m.