Triple
T16865048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rail Safety and Standards Board |
E410015
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway safety organisation |
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 safety organisation Context triple: [Rail Safety and Standards Board, instanceOf, railway safety organisation]
-
A.
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.
-
B.
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.
-
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 portal
A railway portal is a structural entrance or gateway, typically at the mouth of a tunnel or major rail facility, that marks the transition between open track and enclosed or specialized railway infrastructure.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:24 a.m.