Triple
T32931219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shell Crisis of 1915 |
E842404
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military 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: military scandal Context triple: [Shell Crisis of 1915, instanceOf, military 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.
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.
public scandal
A public scandal is a widely known event or series of actions involving perceived wrongdoing or moral failure by individuals or institutions that provokes strong public outrage and media attention.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:20 a.m.