Triple
T22343208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law Enforcement Officers Killed and Assaulted Program |
E552326
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | law enforcement data collection program |
C19484
|
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: law enforcement data collection program Context triple: [Law Enforcement Officers Killed and Assaulted Program, instanceOf, law enforcement data collection program]
-
A.
crime data collection program
chosen
A crime data collection program is a software system that systematically gathers, validates, and stores crime-related information from various sources to support analysis, reporting, and decision-making.
-
B.
law enforcement data
Law enforcement data is information collected, generated, or used by policing and criminal justice agencies about incidents, individuals, activities, and operations for the purposes of investigation, public safety, and legal compliance.
-
C.
crime data program
A crime data program is a software system that collects, stores, analyzes, and visualizes crime-related information to support law enforcement, policy-making, and public safety decision-making.
-
D.
law enforcement system
A law enforcement system is an organized framework of agencies, processes, and technologies designed to prevent, detect, investigate, and respond to violations of laws while upholding public safety and legal rights.
-
E.
law enforcement activity
Law enforcement activity encompasses the actions and operations carried out by authorized agencies and officers to prevent, detect, investigate, and respond to violations of laws and regulations.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:43 p.m.