Triple
T34548457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DfT category C1 |
E886997
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UK railway station classification |
C2007
|
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: UK railway station classification Context triple: [DfT category C1, instanceOf, UK railway station classification]
-
A.
railway station classification
Railway station classification is the conceptual categorization of railway stations based on attributes such as size, passenger volume, services offered, and operational importance within a rail network.
-
B.
railway classification system
A railway classification system is a structured framework used to categorize railways, trains, or rail services based on characteristics such as function, capacity, speed, infrastructure, or ownership.
-
C.
Department for Transport station category
chosen
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.
-
D.
railway location coding system
A railway location coding system is a standardized scheme for assigning unique codes to specific points, facilities, and segments along a rail network to support identification, operations, and data management.
-
E.
group of railway stations
A group of railway stations is a conceptual collection of multiple train stations considered together for purposes such as management, analysis, planning, or classification within a 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.