Triple
T34569255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AK |
E887576
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UK railway location code |
C6436
|
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 location code Context triple: [AK, instanceOf, UK railway location code]
-
A.
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.
-
B.
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.
-
C.
railway location
chosen
A railway location is a specific geographic point or area associated with railway infrastructure, such as stations, junctions, sidings, or signal sites, used for operational, logistical, and reference purposes within a rail network.
-
D.
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.
-
E.
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.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.