Triple
T14703982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Head of Steam – Darlington Railway Museum vicinity |
E345377
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic railway site |
C2895
|
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: historic railway site Context triple: [Head of Steam – Darlington Railway Museum vicinity, instanceOf, historic railway site]
-
A.
heritage railway station
A heritage railway station is a preserved or restored train station that maintains historical architecture, equipment, and operations to reflect and celebrate railway history, often serving tourism and educational purposes.
-
B.
heritage railway
A heritage railway is a preserved or restored railway line operated primarily for historical, educational, and touristic purposes, often using vintage locomotives, rolling stock, and traditional operating practices.
-
C.
railway museum
chosen
A railway museum is a public institution that collects, preserves, and exhibits historic trains, railway equipment, and related artifacts to educate visitors about the history and technology of rail transport.
-
D.
former railway facility
A former railway facility is a decommissioned or repurposed site that once served operational functions for rail transport, such as stations, depots, yards, or maintenance buildings.
-
E.
historical railway interest
Historical railway interest is a fascination with the development, operation, and cultural impact of rail transport throughout history, often involving the study, preservation, and appreciation of trains, routes, infrastructure, and related artifacts.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:28 a.m.