Triple
T17894684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | railway directorates of the USSR |
E447402
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway administrative body |
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 administrative body Context triple: [railway directorates of the USSR, instanceOf, railway administrative body]
-
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.
national railway company
A national railway company is a state-owned or state-controlled organization responsible for operating and managing a country's primary passenger and freight rail transport services and infrastructure.
-
C.
rail safety regulator
A rail safety regulator is an authority responsible for setting, monitoring, and enforcing safety standards and practices across railway systems to protect passengers, workers, and the public.
-
D.
railway infrastructure manager
A railway infrastructure manager is an entity responsible for the planning, construction, maintenance, operation, and safe management of railway tracks, signaling systems, and related fixed installations.
-
E.
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.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:19 a.m.