Triple
T1064265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enron accounting scandal |
E22974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | accounting scandal |
C5263
|
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: accounting scandal Context triple: [Enron accounting scandal, instanceOf, accounting scandal]
-
A.
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.
-
B.
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.
-
C.
sports scandal
A sports scandal is a widely publicized incident in which athletes, teams, or sports organizations engage in unethical, illegal, or rule-breaking behavior that undermines the integrity of competition.
-
D.
baseball scandal
A baseball scandal is a widely publicized incident in which players, teams, or officials violate rules or ethical standards—such as through cheating, gambling, or performance-enhancing drugs—thereby undermining the integrity of the sport.
-
E.
match fixing scandal
A match fixing scandal is a situation in which the outcome or key events of a sports match are illegally manipulated, typically for financial gain through betting or corruption, undermining the integrity of the competition.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:42 p.m.