Triple
T16865001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Railway Safety Regulations 1999 |
E410014
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway safety regulation |
C4226
|
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 regulation Context triple: [Railway Safety Regulations 1999, instanceOf, railway safety regulation]
-
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.
rail safety legislation
chosen
Rail safety legislation comprises the laws and regulations that govern the safe design, operation, maintenance, and oversight of railway systems to protect passengers, workers, and the public.
-
C.
safety regulation
A safety regulation is a formal rule or standard established by authorities or organizations to prevent harm, reduce risk, and protect people, property, and the environment in specific activities or industries.
-
D.
railway technical standard
A railway technical standard is a formalized set of specifications and requirements that define the design, construction, operation, and maintenance criteria for railway systems to ensure safety, interoperability, and performance.
-
E.
railway signaling system
A railway signaling system is an integrated set of trackside and onboard equipment, rules, and communication protocols that control train movements to ensure safe separation, efficient routing, and protection against collisions.
- 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.