Triple
T20364173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CompStat |
E496862
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | data-driven policing approach |
C27440
|
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: data-driven policing approach Context triple: [CompStat, instanceOf, data-driven policing approach]
-
A.
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.
-
B.
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.
-
C.
crime data collection program
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.
-
D.
data-driven government program
chosen
A data-driven government program is an initiative that systematically collects, analyzes, and applies data to design, implement, and continuously improve public policies and services for better outcomes and accountability.
-
E.
policy-relevant data compendium
A policy-relevant data compendium is a curated, structured collection of datasets and indicators organized to inform, support, and evaluate public policy decisions on specific issues or sectors.
- 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:26 a.m.