Triple
T30953087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNISIG |
E788599
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway industry consortium |
C4607
|
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 industry consortium Context triple: [UNISIG, instanceOf, railway industry consortium]
-
A.
railway industry body
chosen
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.
-
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.
rail industry sector
The rail industry sector encompasses companies and organizations involved in the design, manufacture, operation, maintenance, and regulation of railway systems, infrastructure, and rolling stock for freight and passenger transport.
-
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 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.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:53 p.m.