Triple
T9410050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fishguard & Rosslare Railways & Harbours Company |
E226681
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint railway and harbour company |
C26092
|
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: joint railway and harbour company Context triple: [Fishguard & Rosslare Railways & Harbours Company, instanceOf, joint railway and harbour company]
-
A.
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.
-
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.
private railway company
A private railway company is a non-governmental business entity that owns, operates, or manages rail transport services for passengers and/or freight, typically for profit under regulatory oversight.
-
D.
pre-grouping railway company
A pre-grouping railway company is a privately owned or regionally based railway operator in the United Kingdom that existed before the 1923 Railways Act consolidated most railways into the "Big Four" groups.
-
E.
railway company of Russia
A railway company of Russia is an organization that owns, operates, or manages rail transport infrastructure and services within the Russian Federation, including passenger and freight operations.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:47 p.m.