Human Feedback Types
strongPairwise Preference
Directly usable for protocol triage.
"Reward learning typically assumes the human's input covers everything that matters for the task."
HFEPX · Eval paper review
Helena Merker, Nick Walker, Andreea Bobu
Published
Oct 15, 2026
Citations
0
Trust level
Moderate
Usefulness score
57/100 (Medium)
Extraction confidence
65% (Moderate)
Derived from extracted protocol signals and abstract evidence.
Rater population
Not reported
Signals refreshed
Oct 15, 2026
This paper has useful evaluation signal, but protocol completeness is partial; pair it with related papers before deciding implementation strategy.
Use this for comparison and orientation, not as your only source.
Use this page for context, then validate protocol choices against stronger HFEPX references before implementation decisions.
Best use
Secondary protocol comparison source
Use if you need
A secondary eval reference to pair with stronger protocol papers.
What to verify
Read the full paper before copying any benchmark, metric, or protocol choices.
Main weakness
The abstract does not clearly name benchmarks or metrics.
Useful as a secondary reference; validate protocol details against neighboring papers.
If you are doing eval pipeline work, start here
Reward learning typically assumes the human's input covers everything that matters for the task. In practice, humans can only attend to so much at once, so their teaching naturally captures some features---or aspects of the task---better than others. Prior work has shown how the robot can identify which features were poorly supervised directly from its teaching data. But the current solution is to ask the human to try again, putting the burden on someone who already struggled to convey those features. We propose shifting this burden to the robot. Our key insight is that the same information that tells the robot what it doesn't know can help it ask better questions. Preference queries offer a low-effort channel for resolving this uncertainty, but only if the robot knows where to direct them and the human knows what to attend to when answering. We act on this insight in two ways: we build an informed prior that targets preference queries at the features that need resolving, and we accompany each query with an explanation that focuses the human's attention on exactly those features. In simulation, the informed prior beats the standard active preference learning baseline by up to $30.8\%$ in the low-query regime, where reducing human effort matters most. In a user study, the informed prior and explanations each significantly improve reward recovery and amplify each other.
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.
"Reward learning typically assumes the human's input covers everything that matters for the task."
Simulation Env
Includes extracted eval setup.
"Reward learning typically assumes the human's input covers everything that matters for the task."
Not reported
No explicit QC controls found.
"Reward learning typically assumes the human's input covers everything that matters for the task."
Not extracted
No benchmark anchors detected.
"Reward learning typically assumes the human's input covers everything that matters for the task."
Not extracted
No metric anchors detected.
"Reward learning typically assumes the human's input covers everything that matters for the task."
No benchmark or dataset names were extracted from the available abstract.
No metric terms were extracted from the available abstract.
Reward learning typically assumes the human's input covers everything that matters for the task.
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
Detected: Simulation Env
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.