Triple
T2400142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vennbahn railway |
E47746
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic railway |
C1351
|
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: historic railway Context triple: [Vennbahn railway, instanceOf, historic railway]
-
A.
heritage railway
chosen
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.
railway museum
A railway museum is a public institution that collects, preserves, and exhibits historic trains, railway equipment, and related artifacts to educate visitors about the history and technology of rail transport.
-
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.
historic transportation system
A historic transportation system is an organized network of vehicles, routes, and infrastructure from a past era that once facilitated the movement of people or goods and is now preserved, studied, or remembered for its cultural, technological, or historical significance.
-
E.
historic infrastructure
Historic infrastructure comprises long-standing physical structures and systems—such as bridges, roads, canals, and railways—that were built in the past and continue to embody cultural, technological, and architectural significance.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
Created at: March 4, 2026, 7:57 p.m.