MétaCan
Menu
Back to cohort
Record W4403509694 · doi:10.1177/00224278241277815

Partners in Force? Understanding Police Use of Force from a Network Perspective

2024· article· en· W4403509694 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueJournal of Research in Crime and Delinquency · 2024
Typearticle
Languageen
FieldSocial Sciences
TopicCrime Patterns and Interventions
Canadian institutionsSimon Fraser University
Fundersnot available
KeywordsPerspective (graphical)Use of forcePsychologyComputer sciencePolitical scienceLawArtificial intelligence

Abstract

fetched live from OpenAlex

Objectives The importance of peer relations is rooted in decades of policing research; however, scholars have largely overlooked the role of peers in officers’ use-of-force behaviors. The current study investigates the “connected” nature of police use of force. Methods Data on officers’ networks are reconstructed from 11,834 use-of-force reports involving 1,894 officers in seven departments in New Jersey. Exponential Random Graph Models evaluate which officer-level attributes and network dependencies are associated with officers’ co-involvement in police use-of-force incidents. Results Findings indicate the police use of force is not evenly distributed but concentrated on a subset of officers and partnerships. Variation in officers’ likelihood of using force together is driven by individual characteristics, including officer race/ethnicity, rank, and tenure. In addition, co-involvement in force clusters among officers, with officers likely to engage in force together when they share a connection. Conclusion This study highlights an alternative starting point for understanding police use of force. By paying greater attention to the structural makeup of the department, such as the connectivity of the force network, agencies can design efforts that aim to reduce incidents of force through relational properties such as assignments and partnerships.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.107
Threshold uncertainty score0.954

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.504
GPT teacher head0.564
Teacher spread0.061 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it