Triple
T20203977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D03 |
E493299
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transit station identifier |
C7253
|
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: public transit station identifier Context triple: [D03, instanceOf, public transit station identifier]
-
A.
transportation station identifier
A transportation station identifier is a unique code or label assigned to a specific transit facility (such as a train, bus, or metro station) to distinguish it from other stations within a transportation network.
-
B.
public transit station
chosen
A public transit station is a designated facility where passengers can access, board, transfer between, and disembark from public transportation services such as buses, trains, or subways.
-
C.
transport hub identifier
A transport hub identifier uniquely labels a specific transportation node—such as an airport, train station, or bus terminal—to enable unambiguous reference and coordination across systems.
-
D.
transport infrastructure identifier
A transport infrastructure identifier is a unique code or label assigned to specific transportation assets (such as roads, rail lines, bridges, or stations) to enable consistent reference, management, and integration across planning, operations, and data systems.
-
E.
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.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:38 p.m.