Triple
T32870823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professional Standards Division (Liberia National Police) |
E840784
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | police oversight unit |
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: police oversight unit Context triple: [Professional Standards Division (Liberia National Police), instanceOf, police oversight unit]
-
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.
law enforcement unit
A law enforcement unit is an organized group within a policing or security agency tasked with enforcing laws, maintaining public order, and conducting specialized operations or investigations.
-
C.
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.
-
D.
policing support entity
A policing support entity is an organization or unit that assists law enforcement agencies by providing specialized services, resources, or expertise to enhance public safety and policing effectiveness.
-
E.
police operations center
A police operations center is a centralized facility where law enforcement personnel monitor incidents, coordinate field units, manage communications, and make real-time decisions to ensure public safety and effective response.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:17 a.m.