Triple
T9337725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States federal corruption investigation in Detroit |
E224687
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public corruption investigation |
C10249
|
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: public corruption investigation Context triple: [United States federal corruption investigation in Detroit, instanceOf, public corruption investigation]
-
A.
anti-corruption investigation
chosen
An anti-corruption investigation is a systematic inquiry conducted to uncover, document, and address instances of bribery, fraud, abuse of power, or other corrupt practices within public or private institutions.
-
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.
federal investigation
A federal investigation is a formal inquiry conducted by national government agencies to gather evidence, determine whether federal laws have been violated, and support potential enforcement or prosecution actions.
-
D.
judicial investigation
A judicial investigation is a formal, legally authorized inquiry conducted by judicial authorities to gather, examine, and evaluate evidence in order to determine whether laws have been violated and if legal proceedings should follow.
-
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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:40 p.m.