Triple
T10145458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOPAC |
E231694
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | policing oversight body |
C6131
|
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: policing oversight body Context triple: [MOPAC, instanceOf, policing oversight body]
-
A.
police oversight body
chosen
A police oversight body is an independent or semi-independent organization responsible for monitoring, investigating, and reviewing police conduct to ensure accountability, transparency, and public trust in law enforcement.
-
B.
government agency oversight body
A government agency oversight body is an independent or semi-independent entity responsible for monitoring, evaluating, and ensuring that government agencies operate legally, ethically, efficiently, and in alignment with established policies and public interests.
-
C.
law enforcement body
A law enforcement body is an organized governmental agency responsible for maintaining public order, preventing and investigating crime, and enforcing laws within a defined jurisdiction.
-
D.
federal oversight body
A federal oversight body is a government entity responsible for monitoring, evaluating, and enforcing compliance with laws, regulations, and standards across federal agencies or sectors to ensure accountability and integrity.
-
E.
oversight authority
An oversight authority is an independent body or designated entity responsible for monitoring, reviewing, and ensuring that organizations or processes comply with established laws, regulations, standards, and ethical norms.
- 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 9:07 p.m.