Triple
T28596706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millennium Line at Commercial–Broadway station |
E723794
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | SkyTrain station complex |
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: SkyTrain station complex Context triple: [Millennium Line at Commercial–Broadway station, instanceOf, SkyTrain station complex]
-
A.
BTS Skytrain facility
A BTS Skytrain facility is an infrastructure element that supports the operation, maintenance, and management of Bangkok’s elevated rapid transit system, including stations, depots, control centers, and related service areas.
-
B.
Taipei Metro station
A Taipei Metro station is a designated facility within the Taipei rapid transit system where passengers access, board, transfer between, and alight from metro trains, typically featuring platforms, ticketing areas, and passenger amenities.
-
C.
Via Rail station
A Via Rail station is a designated facility where Via Rail passenger trains stop to allow travelers to board, disembark, and access related rail services and amenities.
-
D.
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.
-
E.
Skyline station
A Skyline station is an elevated or ground-level transit facility where passengers board, alight, and transfer between Skyline rail services and other transportation modes.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:22 a.m.