Triple
T38320643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSHA whistleblower protection programs |
E1036656
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal enforcement program |
C357
|
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: federal enforcement program Context triple: [OSHA whistleblower protection programs, instanceOf, federal enforcement program]
-
A.
federal enforcement order
A federal enforcement order is a legally binding directive issued by a federal authority requiring specific actions or compliance to enforce federal laws, regulations, or judgments.
-
B.
federal civil enforcement action
A federal civil enforcement action is a non-criminal lawsuit brought by a U.S. federal agency or the Department of Justice to compel compliance with federal laws, regulations, or orders and to obtain remedies such as injunctions, penalties, or restitution.
-
C.
federal government program
chosen
A federal government program is an organized set of activities, services, or regulations funded and administered by the national government to achieve specific public policy goals.
-
D.
infractions program
An infractions program is a structured system for identifying, recording, and managing violations of rules or policies, along with their corresponding consequences.
-
E.
federal conservation program suite
A federal conservation program suite is an integrated set of government-administered initiatives, policies, and funding mechanisms designed to protect, restore, and sustainably manage natural resources and ecosystems across jurisdictions.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.