Human Feedback Types
strongRubric Rating
Directly usable for protocol triage.
"As LLM-based agents develop, they have been increasingly applied in the legal domain."
HFEPX · Eval paper review
Xinyu Yang, Jiejun Tan, Chenlong Deng, Chenghao Zhang +2 more
Published
Nov 4, 2026
Citations
0
Trust level
Moderate
Usefulness score
40/100 (Low)
Extraction confidence
50% (Moderate)
Derived from extracted protocol signals and abstract evidence.
Rater population
Not reported
Signals refreshed
Nov 4, 2026
This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.
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
Background context only
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.
Treat as adjacent context, not a core eval-method reference.
If you are doing eval pipeline work, start here
As LLM-based agents develop, they have been increasingly applied in the legal domain. Legal Judgment Prediction~(LJP) requires models to conduct multi-step reasoning and external legal evidence retrieval. Existing legal search agents' performance is often constrained by the quality of retrieval queries. They often formulate queries directly from the initial user request, overlooking latent legal issues and legally salient details. To address this issue, we propose \emph{LegalEvolver}, a query optimization framework specifically designed to generate legally informative queries for LJP-oriented retrieval. Sampling high-quality optimized queries and their corresponding search trajectories is challenging, as relying solely on unguided high-temperature rollouts is both inefficient and constrained by the model's initial capabilities. We therefore heuristically optimize queries as seeds, improving the efficiency of trajectory generation. Furthermore, we summarize rollout experience into rubrics and use them to guide multi-round iterative self-evolution. Iteratively performing rubric optimization and rubric-guided RL enables the model to surpass its initial performance ceiling. End-to-end performance on extensive benchmarks demonstrates the effectiveness of query optimization on LJP. Comparisons with direct SFT followed by RL demonstrate the effectiveness of rubric guidance. Evolving rubrics further outperform fixed rubrics, confirming the benefits of self-evolution.
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.
Rubric Rating
Directly usable for protocol triage.
"As LLM-based agents develop, they have been increasingly applied in the legal domain."
None explicit
Validate eval design from full paper text.
"As LLM-based agents develop, they have been increasingly applied in the legal domain."
Not reported
No explicit QC controls found.
"As LLM-based agents develop, they have been increasingly applied in the legal domain."
Not extracted
No benchmark anchors detected.
"As LLM-based agents develop, they have been increasingly applied in the legal domain."
Not extracted
No metric anchors detected.
"As LLM-based agents develop, they have been increasingly applied in the legal domain."
No benchmark or dataset names were extracted from the available abstract.
No metric terms were extracted from the available abstract.
As LLM-based agents develop, they have been increasingly applied in the legal domain.
Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.
Human feedback protocol is explicit
Detected: Rubric Rating
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.