Triple
T12549519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Investigation Unit |
E300060
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | elite investigative division |
C3496
|
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: elite investigative division Context triple: [Special Investigation Unit, instanceOf, elite investigative division]
-
A.
criminal investigation unit
A criminal investigation unit is a specialized law enforcement team responsible for systematically gathering, analyzing, and preserving evidence to identify suspects, solve crimes, and support successful prosecution.
-
B.
investigative agency
An investigative agency is an organized entity that conducts systematic inquiries and gathers evidence to uncover facts, resolve disputes, or support legal and security-related decisions.
-
C.
law enforcement unit
chosen
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.
-
D.
intelligence agency division
A specialized organizational unit within an intelligence agency responsible for focused functions such as collection, analysis, operations, or support in pursuit of national security objectives.
-
E.
Kansas Bureau of Investigation agent
A Kansas Bureau of Investigation agent is a state-level law enforcement officer responsible for conducting criminal investigations, gathering and analyzing evidence, and supporting local agencies to uphold public safety and enforce Kansas laws.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:58 p.m.