Triple
T1371991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London King’s Cross |
E30132
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway station in London |
C564
|
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 in London Context triple: [London King’s Cross, instanceOf, railway station in London]
-
A.
train station
chosen
A train station is a designated facility where trains regularly stop to pick up and drop off passengers and sometimes freight, typically featuring platforms, ticketing services, and waiting areas.
-
B.
railway bridge terminus
A railway bridge terminus is the endpoint of a rail line where tracks transition from or onto a bridge structure, often incorporating platforms, signaling, and facilities for train arrival, departure, and turnaround.
-
C.
railway station in Scotland
A railway station in Scotland is a designated facility along the Scottish rail network where trains stop to allow passengers to board and alight, often providing ticketing, waiting areas, and connections to local transport services.
-
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.
commuter rail station
A commuter rail station is a designated facility where passengers board and alight regional trains that connect suburbs or outlying areas with urban centers, typically offering platforms, ticketing, and basic passenger amenities.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:57 p.m.