Triple
T35246145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tripping of linesman Ron Foyt |
E1017666
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | abuse of official case |
C61799
|
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: abuse of official case Context triple: [Tripping of linesman Ron Foyt, instanceOf, abuse of official case]
-
A.
misuse of private information case
A misuse of private information case is a legal action where a claimant alleges that another party wrongfully accessed, disclosed, or exploited their confidential or personal information without consent, causing harm or distress.
-
B.
whistleblowing case
A whistleblowing case is an instance in which an individual reports suspected wrongdoing, misconduct, or illegal activity within an organization to internal or external authorities, triggering formal review or investigation.
-
C.
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.
-
D.
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.
-
E.
prisoner abuse incident
A prisoner abuse incident is a documented event in which an incarcerated individual is subjected to unlawful, unethical, or excessive physical, psychological, or sexual harm by authorities or other inmates within a custodial setting.
- 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.