Triple
T5513141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | childcare benefits scandal |
E144615
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative scandal |
C19132
|
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: administrative scandal Context triple: [childcare benefits scandal, instanceOf, administrative scandal]
-
A.
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.
-
B.
political scandal
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.
-
C.
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.
-
D.
sexual misconduct scandal
A sexual misconduct scandal is a widely publicized controversy involving allegations or revelations of inappropriate, non-consensual, or exploitative sexual behavior by an individual or group, often leading to public outrage, legal consequences, and reputational damage.
-
E.
financial scandal
A financial scandal is a widely publicized incident in which individuals or organizations engage in unethical, illegal, or deceptive financial practices that result in significant economic harm, loss of trust, or legal consequences.
- F. None of above. chosen
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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:33 p.m.