Triple
T23437170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WLO |
E563495
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway station identifier |
C1043
|
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: railway station identifier Context triple: [WLO, instanceOf, railway 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.
railway station code
chosen
A railway station code is a short alphanumeric identifier assigned to a specific train station to uniquely reference it in timetables, ticketing, and railway operations.
-
C.
IATA-like rail station code
A short, standardized alphanumeric identifier assigned to a railway station, analogous to IATA airport codes, used to uniquely reference stations in timetables, ticketing, and operational 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.
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.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 5:50 p.m.