Triple
T26000530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic Rail Adventures LLC |
E646607
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage rail company |
C17972
|
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 rail company Context triple: [Historic Rail Adventures LLC, instanceOf, heritage rail company]
-
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
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 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.
railway holding company
A railway holding company is a parent corporation that owns and controls one or more railway operating or infrastructure companies, managing their strategic direction and financial interests without necessarily running day-to-day train operations itself.
-
E.
heritage transport operator
chosen
A heritage transport operator is an organization or individual that preserves, maintains, and runs historic vehicles or transport services, often for educational, cultural, or touristic purposes.
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 8:58 a.m.