Triple
T21422479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | toeslagenaffaire |
E528470
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public administration scandal |
C333
|
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: public administration scandal Context triple: [toeslagenaffaire, instanceOf, public administration scandal]
-
A.
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.
-
B.
criminal scandal
A criminal scandal is a widely publicized incident in which illegal or morally corrupt actions by individuals or organizations are exposed, often leading to public outrage, legal consequences, and reputational damage.
-
C.
political scandal
chosen
A political scandal is a widely publicized incident in which public officials or institutions are implicated in unethical, illegal, or corrupt behavior that undermines public trust.
-
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.
legal scandal
A legal scandal is a widely publicized controversy arising from alleged or proven violations of law or ethical standards by individuals or organizations, often involving misconduct, corruption, or abuse of power.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 5:48 p.m.