Triple
T19259731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATEX Directive |
E481613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | occupational safety regulation |
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: occupational safety regulation Context triple: [ATEX Directive, instanceOf, occupational safety regulation]
-
A.
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.
-
B.
occupational safety and health code of practice
An occupational safety and health code of practice is a structured set of guidelines and minimum standards that organizations must follow to systematically identify, control, and manage workplace hazards to protect workers’ health, safety, and welfare.
-
C.
occupational safety and health bulletin
An occupational safety and health bulletin is an official communication document that provides workers and employers with concise, authoritative information, alerts, and guidance on preventing workplace injuries, illnesses, and hazards.
-
D.
public safety occupation
A public safety occupation is a role in which individuals work to protect the health, safety, and welfare of the public by preventing, responding to, and mitigating emergencies, hazards, and threats.
-
E.
occupational safety and health research framework
A structured, systematic model that guides the planning, conduct, evaluation, and translation of studies aimed at understanding and improving workplace safety, health, and well-being.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:28 p.m.