Triple
T26000531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic Rail Adventures LLC |
E646607
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tourist railroad operator |
C15754
|
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: tourist railroad operator Context triple: [Historic Rail Adventures LLC, instanceOf, tourist railroad operator]
-
A.
mountain railroad
A mountain railroad is a railway system specifically engineered to traverse steep, rugged mountainous terrain, often using special track layouts, gradients, and locomotives to handle sharp elevation changes and curves.
-
B.
rail transport attraction
chosen
A rail transport attraction is a tourism-focused facility or experience centered around trains, railways, or rail-related activities, designed to entertain, educate, or provide unique travel experiences to visitors.
-
C.
transport infrastructure operator
A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
-
D.
mountain rack railway
A mountain rack railway is a steep-gradient railway system that uses a toothed rack rail engaged by a cogwheel on the train to provide additional traction and braking on mountainous terrain.
-
E.
tour operator
A tour operator is a business or individual that designs, organizes, and sells packaged travel experiences, coordinating transportation, accommodation, activities, and other services for travelers.
- 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.