Field noteOct 15, 20262 min read1 source

SoSBench benchmarks LLM safety across six regulated scientific domains with 3,000 knowledge-intensive prompts ( paper ).

In one minute

**Thesis:** Safety evaluation needs to test hazardous requests that require domain knowledge, not only simple prohibited instructions.

Mechanism: SoSBench grounds 3,000 prompts in real-world laws and regulations, then uses an LLM-assisted evolutionary pipeline to create varied misuse scenarios across six scientific domains. Why now: The paper reports harmful-response rates of 84.9% for DeepSeek-R1 and 50.3% for GPT-4.1 under its evaluation, making the gap visible in tests of advanced models. Evidence boundary: These are benchmark results reported by the paper; they do not establish how often models behave this way in production or how representative the prompts are of actual use.

The benchmark covers chemistry, biology, medicine, pharmacology, physics and psychology. The authors contrast its knowledge-intensive scenarios with prior safety tests based on low-comprehension instructions or lower-risk question formats. The mechanism matters because refusals can appear reliable on simple prompts while failing when a harmful request is framed with specialist concepts. First implication: Teams evaluating models for scientific or regulated workflows should add domain-specific misuse scenarios to safety testing rather than treating generic refusal scores as sufficient.

SoSBench gives evaluators a concrete test set and unified framework, but the reported percentages should be read within that framework. The supplied paper summary does not establish independent replication, deployment prevalence, or the quality of every generated prompt. First watch condition: Look for independent evaluations that rerun SoSBench or compare its results with real-world incident and red-team evidence. This starts a distinct analytical record because no prior New Runtime record on this benchmark was supplied; the available archive entries concern other evaluation questions, not this domain-specific safety test.

Evidence / sources

  1. 1arxiv.org/abs/2505.21605
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicPromptsExplore the prompts topic hub.
  2. 02archiveField NotesOpen the latest editorial analysis.
  3. 03source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract