Triple
T33691256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kemsley Down depot |
E863186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage railway infrastructure |
C41535
|
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: heritage railway infrastructure Context triple: [Kemsley Down depot, instanceOf, heritage railway infrastructure]
-
A.
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.
-
B.
heritage tramway system
A heritage tramway system is a historically preserved or recreated tram network operated primarily for cultural, educational, and touristic purposes, often using restored vintage vehicles and traditional infrastructure.
-
C.
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.
-
D.
historical railway asset
chosen
A historical railway asset is any preserved or documented physical or digital artifact—such as tracks, rolling stock, stations, equipment, or records—associated with past railway operations and valued for its cultural, technological, or historical significance.
-
E.
railway infrastructure element
A railway infrastructure element is any physical component of a rail system—such as tracks, signals, switches, bridges, or platforms—that supports the safe and efficient operation of trains.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:43 a.m.