Triple
T37181891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HarbourFront MRT station |
E921213
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mass Rapid Transit interchange 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: Mass Rapid Transit interchange station Context triple: [HarbourFront MRT station, instanceOf, Mass Rapid Transit interchange station]
-
A.
London Underground interchange
A London Underground interchange is a station or complex where passengers can transfer between two or more Underground lines (and sometimes other rail services) within a single integrated facility.
-
B.
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.
-
C.
railway–metro interchange
A railway–metro interchange is a transport facility where mainline railway services and urban metro lines connect, enabling passengers to transfer conveniently between regional and local rail networks.
-
D.
ION rapid transit station
An ION rapid transit station is a designated stop along the ION light rail or bus rapid transit network that provides platforms, passenger amenities, and access points for boarding and alighting ION vehicles.
-
E.
group of metro interchange stations
A group of metro interchange stations is a collection of transit hubs where multiple metro lines intersect, enabling passengers to transfer between routes within an urban rail network.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.