Triple
T25788484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulatory Reform (Fire Safety) Order 2005 |
E649485
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fire safety legislation |
C10033
|
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: fire safety legislation Context triple: [Regulatory Reform (Fire Safety) Order 2005, instanceOf, fire safety legislation]
-
A.
fire service standard
A fire service standard is a formalized set of criteria, procedures, and performance requirements that guide the organization, operation, safety, and effectiveness of fire and emergency response services.
-
B.
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.
-
C.
safety regulation
chosen
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.
fire prevention engineer
A fire prevention engineer is a professional who designs, evaluates, and implements systems, codes, and strategies to minimize fire risks and ensure life safety in buildings and facilities.
-
E.
fire safety equipment manufacturer
A fire safety equipment manufacturer is a company that designs, produces, and supplies devices and systems such as fire extinguishers, alarms, sprinklers, and protective gear to prevent, detect, and control fires in residential, commercial, and industrial settings.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 5:57 a.m.