Triple
T13188512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheshire Lines Committee |
E313921
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint railway committee |
C29184
|
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 committee Context triple: [Cheshire Lines Committee, instanceOf, joint railway committee]
-
A.
joint railway
chosen
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.
-
B.
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.
-
C.
public railway
A public railway is a government- or publicly-owned rail transport system that provides scheduled passenger and/or freight services accessible to the general population, typically operating on standardized tracks and infrastructure.
-
D.
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.
-
E.
railway industry body
A railway industry body is an organization that represents, coordinates, and sets standards or policies for companies and stakeholders involved in the rail transport sector.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:15 p.m.