Triple
T12105998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afghan War Diary leak |
E288305
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | whistleblowing event |
C17238
|
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: whistleblowing event Context triple: [Afghan War Diary leak, instanceOf, whistleblowing event]
-
A.
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.
-
B.
whistleblower protection law
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.
-
C.
administrative scandal
An administrative scandal is a public controversy arising from serious misconduct, corruption, or ethical violations within an organization’s management or bureaucratic processes.
-
D.
accounting scandal
An accounting scandal is a situation in which a company or organization intentionally manipulates or falsifies financial records to mislead stakeholders about its true financial performance or condition.
-
E.
mass surveillance revelation
chosen
A mass surveillance revelation is the public disclosure of previously hidden, large-scale monitoring of individuals or populations by governments or organizations, exposing the scope, methods, and implications of such surveillance.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:49 p.m.