Triple
T37309283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaragoza-Portillo station as main long-distance station |
E926160
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical railway role |
C66320
|
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 role Context triple: [Zaragoza-Portillo station as main long-distance station, instanceOf, historical railway role]
-
A.
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.
-
B.
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.
-
C.
former railway
A former railway is a decommissioned rail line or route that once carried train traffic but has since been abandoned, removed, or repurposed for other uses.
-
D.
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.
-
E.
former railway facility
A former railway facility is a decommissioned or repurposed site that once served operational functions for rail transport, such as stations, depots, yards, or maintenance buildings.
- F. None of above. chosen
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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.