Triple
T28453369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UGOFE |
E716639
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway consortium |
C14575
|
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 consortium Context triple: [UGOFE, instanceOf, railway consortium]
-
A.
group of railway companies
chosen
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.
-
B.
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.
-
C.
railway construction company
A railway construction company is an organization that plans, designs, and builds railway infrastructure, including tracks, stations, bridges, and related systems, often coordinating engineering, procurement, and project management activities.
-
D.
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.
-
E.
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.
- 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 28, 2026, 1:53 a.m.