Triple
T28899904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EN 50128 |
E732925
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway safety standard |
C17465
|
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 standard Context triple: [EN 50128, instanceOf, railway safety standard]
-
A.
railway technical standard
chosen
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.
-
B.
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.
-
C.
rail safety legislation
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.
-
D.
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.
-
E.
railway locomotive standardization scheme
A railway locomotive standardization scheme is a systematic framework for defining, organizing, and unifying the design, classification, and specifications of locomotives across a rail network to ensure compatibility, efficiency, and ease of maintenance.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 8:01 a.m.