Triple
T3417845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newark Castle railway station |
E72052
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway station in England |
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 England Context triple: [Newark Castle railway station, instanceOf, railway station in England]
-
A.
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.
-
B.
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.
-
C.
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.
-
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.
former railway station
A former railway station is a decommissioned train facility that once served passengers or freight but is no longer in active railway use.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:15 p.m.