Triple
T13286320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECT |
E316453
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Transport for London station code |
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: Transport for London station code Context triple: [ECT, instanceOf, Transport for London station code]
-
A.
railway station code
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.
-
B.
Department for Transport station category
A Department for Transport station category is a classification assigned by the UK Department for Transport that groups railway stations into standardized categories based on factors such as passenger usage, facilities, and strategic importance.
-
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.
Amtrak station code
An Amtrak station code is a unique three-letter identifier assigned to each train station served by Amtrak for use in reservations, ticketing, and operations.
-
E.
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.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:27 p.m.