Triple
T10145694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Health and Safety at Work etc. Act 1974 |
E231699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health and 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: health and safety legislation Context triple: [Health and Safety at Work etc. Act 1974, instanceOf, health and safety legislation]
-
A.
health legislation
Health legislation comprises the laws and regulations enacted to organize, finance, deliver, and oversee public and private health services, protect public health, and safeguard patients’ rights.
-
B.
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.
-
C.
health and safety initiative
A health and safety initiative is a coordinated program of policies, practices, and interventions designed to prevent injuries and illnesses, promote well-being, and ensure a safe environment for individuals in a specific setting or community.
-
D.
public health law
Public health law is the body of legal rules, powers, and duties that governments use to prevent disease, promote health, and protect populations while balancing individual rights and community interests.
-
E.
public health regulation
Public health regulation is the body of laws, policies, and administrative rules designed to protect and promote population health by controlling risks, guiding health behaviors, and ensuring safe environments, products, and services.
- 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 9:07 p.m.