Triple
T3634355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rampart scandal |
E77031
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | law enforcement misconduct case |
C10783
|
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: law enforcement misconduct case Context triple: [Rampart scandal, instanceOf, law enforcement misconduct case]
-
A.
police brutality incident
chosen
A police brutality incident is an event in which law enforcement officers use excessive, unwarranted, or illegal force or misconduct against civilians, resulting in physical, psychological, or civil rights harm.
-
B.
miscarriage of justice
Miscarriage of justice is a serious failure of the legal system in which an individual is wrongly convicted, punished, or otherwise denied a fair and accurate legal outcome.
-
C.
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.
-
D.
murder case
A murder case is a legal investigation and prosecution concerning the unlawful killing of one person by another, encompassing evidence collection, suspect identification, and judicial proceedings to determine guilt and assign punishment.
-
E.
victim of police violence
A victim of police violence is an individual who has suffered physical, psychological, or civil rights harm as a result of excessive, unlawful, or discriminatory actions by law enforcement officers.
- 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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:24 p.m.