Triple
T17069301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Pacific Heritage Fleet |
E414171
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rail preservation program |
C5247
|
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: rail preservation program Context triple: [Union Pacific Heritage Fleet, instanceOf, rail preservation program]
-
A.
heritage conservation programme
A heritage conservation programme is an organized set of policies, actions, and resources aimed at identifying, protecting, and sustainably managing cultural and natural heritage for present and future generations.
-
B.
Amtrak program
An Amtrak program is an organized set of services, policies, and initiatives designed to manage and enhance passenger rail operations, customer experience, and related business objectives within the Amtrak system.
-
C.
historic preservation project
chosen
A historic preservation project is a coordinated effort to identify, protect, restore, and maintain buildings, sites, or artifacts of historical, cultural, or architectural significance for present and future generations.
-
D.
railway modernisation project
A railway modernisation project is an initiative that upgrades existing rail infrastructure, technology, and operations to improve capacity, safety, efficiency, and passenger experience.
-
E.
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.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:34 a.m.