Triple
T27149855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sortavala–Matkaselkä railway |
E682356
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical railway line |
C3787
|
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: historical railway line Context triple: [Sortavala–Matkaselkä railway, instanceOf, historical railway line]
-
A.
railway line
chosen
A railway line is a fixed transportation route consisting of tracks, signaling, and related infrastructure along which trains operate between defined locations.
-
B.
historic railroad right-of-way
A historic railroad right-of-way is a corridor of land formerly used for railroad tracks and associated infrastructure that retains cultural, transportation, or engineering significance despite no longer serving active rail operations.
-
C.
historical railway interest
Historical railway interest is a fascination with the development, operation, and cultural impact of rail transport throughout history, often involving the study, preservation, and appreciation of trains, routes, infrastructure, and related artifacts.
-
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 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:13 a.m.