aceModerate evidence
Published recordCrimeProblem Space
More
Human and AI judgements of restorative responses to sexual abuse: The role of perceived severity
- Truvace record
- TRV-2026-2512raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- 1a3b5b8d0693…check it
Abstract Purpose Restorative justice (RJ) offers an alternative or complement to criminal justice in sexual abuse cases, yet the public remains ambivalent. Given that survivors increasingly turn to large language models (LLMs) for information and support when coping with sensitive justice‐related decisions, the present study examined whether the guidance LLMs provide regarding RJ in sexual abuse cases resembles human views. Methods Participants ( N = 469) were randomly assigned to read a vignette describing intr…
The problem
In a study comparing 469 people with 120 outputs from Gemini, Grok and DeepSeek, the chatbots gave significantly higher support ratings for restorative justice after sexual abuse than humans did, a gap that matters for survivors who ask AI for guidance.
What this doesn’t fix
The chatbot ratings were generated under structured prompting conditions, and the authors say the higher support held under the conditions used, so results may differ with other prompts or real survivor conversations.
Sources
1 on file- Legal and Criminological Psychologydoi:10.1111/lcrp.70053
Cite this record
v1Truvace Impact Record TRV-2026-2512, v1: “Human and AI judgements of restorative responses to sexual abuse: The role of perceived severity.” Truvace, 2026-11-12. /record/TRV-2026-2512 (accessed on the day you copy it). sha256 1a3b5b8d069310f6…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2512 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.