Triple
T33104315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Critical Incident Response |
E847145
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kentucky State Police division |
C3704
|
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: Kentucky State Police division Context triple: [Critical Incident Response, instanceOf, Kentucky State Police division]
-
A.
division of Virginia State Police
A division of the Virginia State Police is a regional or functional organizational unit responsible for administering and coordinating law enforcement, public safety, and support services within a specific geographic area or specialized domain in the Commonwealth of Virginia.
-
B.
county of Kentucky
A county of Kentucky is a local governmental and geographic subdivision of the Commonwealth of Kentucky, responsible for regional administration, services, and jurisdiction within its defined boundaries.
-
C.
state police agency
chosen
A state police agency is a government law enforcement organization with statewide jurisdiction responsible for enforcing laws, maintaining public order, and supporting local agencies across the entire state.
-
D.
Shawnee division
Shawnee division refers to a specific subgroup or organizational unit associated with the Shawnee people, typically distinguished by geographic location, lineage, or administrative function.
-
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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:26 a.m.