Triple
T38604960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serco-Abellio joint venture |
E934316
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway operating company joint venture |
C9409
|
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 operating company joint venture Context triple: [Serco-Abellio joint venture, instanceOf, railway operating company joint venture]
-
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.
group of railway companies
A group of railway companies is an organized association of multiple rail transport operators that collaborate or are collectively managed to provide coordinated rail services, share resources, or pursue common commercial or regulatory interests.
-
C.
joint railway
A joint railway is a rail line or network that is owned, operated, or managed collaboratively by two or more railway companies or authorities, sharing infrastructure, services, and responsibilities.
-
D.
rail transport company
chosen
A rail transport company is an organization that owns, operates, or manages trains and railway infrastructure to provide freight and/or passenger transportation services.
-
E.
joint railway and harbour company
A joint railway and harbour company is an organization that owns and operates both rail transport infrastructure and port facilities, coordinating the movement of goods and passengers between land and sea.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.