Triple
T20777563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vhg |
E511392
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport station identifier |
C25686
|
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 transport station identifier Context triple: [Vhg, instanceOf, public transport station identifier]
-
A.
transportation station identifier
chosen
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.
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.
-
C.
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.
-
D.
ship station identifier
A ship station identifier is a unique code or designation assigned to a specific ship’s radio or communication station to distinguish it from all other maritime stations.
-
E.
public transit station
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.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:37 p.m.