Triple
T19539500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roundhouse Park |
E488857
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway heritage site |
C2895
|
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: railway heritage site Context triple: [Roundhouse Park, instanceOf, railway heritage site]
-
A.
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.
-
B.
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.
-
C.
railway museum
chosen
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.
-
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.
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.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:41 p.m.