Triple
T25184678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barry Railway |
E630684
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic railway company |
C4887
|
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 company Context triple: [Barry Railway, instanceOf, historic railway company]
-
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.
street railway company
A street railway company is a business entity that owns, operates, and maintains streetcars or trams running on fixed rails along public streets to provide urban passenger transportation.
-
C.
historic company
chosen
A historic company is an established business organization that has operated over a significant period of time and is notable for its enduring impact, legacy, or role in historical events or developments.
-
D.
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.
-
E.
railway holding company
A railway holding company is a parent corporation that owns and controls one or more railway operating or infrastructure companies, managing their strategic direction and financial interests without necessarily running day-to-day train operations itself.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 12:37 p.m.