Triple
T29459808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Western Railway carriages |
E747200
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage rolling stock |
C38765
|
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 rolling stock Context triple: [Great Western Railway carriages, instanceOf, heritage rolling stock]
-
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 railroad fleet
chosen
A heritage railroad fleet is a collection of historically significant locomotives and rolling stock preserved, maintained, and operated to represent and interpret past eras of railway transportation.
-
C.
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.
-
D.
historical railway asset
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.
heritage streetcar
A heritage streetcar is a restored or replica electric tram operated primarily for historical preservation, tourism, or nostalgic public transit experiences, often using vintage vehicles and traditional infrastructure.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 3:48 p.m.