Triple
T10281472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fox News sexual harassment scandal |
E241110
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sexual harassment scandal |
C1745
|
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: sexual harassment scandal Context triple: [Fox News sexual harassment scandal, instanceOf, sexual harassment scandal]
-
A.
sexual misconduct scandal
chosen
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.
-
B.
media scandal
A media scandal is a widely publicized controversy, often involving alleged wrongdoing or ethical breaches by public figures or institutions, that attracts intense and sustained news coverage and public scrutiny.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:39 a.m.