Triple
T38320642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSHA whistleblower protection programs |
E1036656
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | whistleblower protection program |
C26262
|
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: whistleblower protection program Context triple: [OSHA whistleblower protection programs, instanceOf, whistleblower protection program]
-
A.
whistleblower protection law
chosen
A whistleblower protection law is a legal framework that safeguards individuals who report wrongdoing or illegal activities from retaliation by their employers or other entities.
-
B.
whistleblower
A whistleblower is an individual who exposes information or activities within an organization that are deemed illegal, unethical, or otherwise improper, typically to authorities, regulators, or the public.
-
C.
whistleblowing platform
A whistleblowing platform is a secure, often anonymous digital system that enables individuals to report misconduct, fraud, or unethical behavior to appropriate authorities or oversight bodies.
-
D.
whistleblowing case
A whistleblowing case is an instance in which an individual reports suspected wrongdoing, misconduct, or illegal activity within an organization to internal or external authorities, triggering formal review or investigation.
-
E.
witness protection program
A witness protection program is a government-run system that safeguards threatened witnesses and their families by providing security, relocation, and new identities in exchange for their cooperation in legal proceedings.
- 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.