MétaCan
Menu
Back to cohort
Record W2099145840 · doi:10.1017/s1743923x10000280

Should International Relations Consider Rape a Weapon of War?

2010· article· en· W2099145840 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

VenuePolitics & Gender · 2010
Typearticle
Languageen
FieldSocial Sciences
TopicGender, Security, and Conflict
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsCategorizationPower (physics)Political scienceSoftware deploymentCriminologyComputer securityInternational relationsSociologyLawEpistemologyEngineeringComputer sciencePolitics

Abstract

fetched live from OpenAlex

This article argues that systematic rape should be conceptualized not only as a war crime, but also as a destructive and increasingly deployed war weapon. As such, rape becomes a subject of arms control and thus directly relevant to security studies. Consequently, I argue that international relations should consider rape as a weapon of war for two major reasons. First, the categorization of rape as a weapon of war fits with core disciplinary theoretical definitions and assumptions. Namely, rape as a weapon of war compromises state security, operates in a conception of power defined as material/“power-over”/zero-sum, and corresponds with a rational actor model. Second, although wartime rape has often been marginalized as a “women's issue,” empirical evidence persuasively demonstrates how this categorization is incomplete; rather, women, girls, men, and boys all suffer direct and/or indirect consequences from the increasing prevalence and brutality of this weapon's deployment. Overall, the article maintains that excluding rape from security studies precludes comprehensive, accurate analysis within areas of theoretical and practical concern to IR. Thus, I conclude by suggesting avenues of research, from diverse theoretical perspectives, that may persuade IR scholars to view rape as an increasingly relevant and analytically rich topic of study.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.767
Threshold uncertainty score0.998

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0030.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.101
GPT teacher head0.377
Teacher spread0.276 · 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