Human Feedback Types
partialPairwise Preference
Directly usable for protocol triage.
"While reasoning models have achieved remarkable success in complex reasoning tasks, their increasing power necessitates stringent safety measures."
HFEPX · Eval paper review
Yanbo Wang, Minzheng Wang, Jian Liang, Lu Wang +2 more
Published
Feb 14, 2026
Citations
0
Trust level
Low
Usefulness score
40/100 (Low)
Extraction confidence
45% (Low)
Derived from extracted protocol signals and abstract evidence.
Rater population
Not reported
Signals refreshed
Jun 29, 2026
This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.
Use this as background context only. Do not make protocol decisions from this page alone.
Use this page for context, then validate protocol choices against stronger HFEPX references before implementation decisions.
Best use
Background context only
Use if you need
Background context only.
What to verify
Read the full paper before copying any benchmark, metric, or protocol choices.
Main weakness
The available metadata is too thin to trust this as a primary source.
Treat as adjacent context, not a core eval-method reference.
If you are doing eval pipeline work, start here
While reasoning models have achieved remarkable success in complex reasoning tasks, their increasing power necessitates stringent safety measures. For safety alignment, the core challenge lies in the inherent trade-off between safety and utility. However, prevailing alignment strategies typically construct CoT training data with explicit safety rules via context distillation. This approach inadvertently limits reasoning capabilities by creating a rigid association between rule memorization and refusal. To mitigate the safety-utility trade-off, we propose the Adaptive Safe Context Learning~(ASCL) framework to improve the reasoning given proper context. ASCL formulates safety alignment as a multi-turn tool-use process, empowering the model to autonomously decide when to consult safety rules and how to generate the ongoing reasoning. Furthermore, to counteract the preference for rule consultation during RL, we introduce Inverse Frequency Policy Optimization~(IFPO) to rebalance advantage estimates. By decoupling rule retrieval and subsequent reasoning, our method achieves higher overall performance compared to baselines. Our code is publicly available at https://github.com/ybwang119/ASCL.
These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.
Pairwise Preference
Directly usable for protocol triage.
"While reasoning models have achieved remarkable success in complex reasoning tasks, their increasing power necessitates stringent safety measures."
None explicit
Validate eval design from full paper text.
"While reasoning models have achieved remarkable success in complex reasoning tasks, their increasing power necessitates stringent safety measures."
Not reported
No explicit QC controls found.
"While reasoning models have achieved remarkable success in complex reasoning tasks, their increasing power necessitates stringent safety measures."
Not extracted
No benchmark anchors detected.
"While reasoning models have achieved remarkable success in complex reasoning tasks, their increasing power necessitates stringent safety measures."
Not extracted
No metric anchors detected.
"While reasoning models have achieved remarkable success in complex reasoning tasks, their increasing power necessitates stringent safety measures."
No benchmark or dataset names were extracted from the available abstract.
No metric terms were extracted from the available abstract.
While reasoning models have achieved remarkable success in complex reasoning tasks, their increasing power necessitates stringent safety measures.
Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.
Human feedback protocol is explicit
Detected: Pairwise Preference
Evaluation mode is explicit
No clear evaluation mode extracted.
Quality control reporting appears
No calibration/adjudication/IAA control explicitly detected.
Benchmark or dataset anchors are present
No benchmark/dataset anchor extracted from abstract.
Metric reporting is present
No metric terms extracted.