Human Feedback Types
missingNone explicit
No explicit feedback protocol extracted.
"Extensive context has become the norm as Large Language Models (LLMs) are increasingly deployed in long-horizon tasks."
HFEPX · Eval paper review
Shijie Xia, Yikun Wang, Zhen Huang, Pengfei Liu
Published
Jun 29, 2026
Citations
0
Trust level
Low
Usefulness score
25/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
A secondary eval reference to pair with stronger protocol papers.
What to verify
Validate the evaluation procedure and quality controls in the full paper before operational use.
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
Extensive context has become the norm as Large Language Models (LLMs) are increasingly deployed in long-horizon tasks. The concern that increasing context length degrades model capabilities, known as context rot, has become a central issue for these applications. In this paper, we focus on deep search scenarios, aiming to investigate the rot phenomenon and its mitigation strategies. By evaluating four flagship open-source models across three benchmarks, we reveal a prevalent but unnoticed rot phenomenon: extensive context causes models to directly give up or prematurely provide uncertain answers, and this issue is exacerbated as the context grows. Through pruning experiments, we demonstrate the relationship between the accumulated context and the rot phenomenon. Furthermore, we investigate mitigating this issue through context management and post-hoc rejection sampling. For context management, we systematically evaluate seven different methods across three categories, based on performance, cost, and impact on context rot, providing clear guidance for strategy selection and usage. For rejection sampling, we develop a rot-aware filtering strategy and demonstrate its effectiveness across three aggregation methods. Finally, we show that these two approaches can be combined for further performance improvements.
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.
None explicit
No explicit feedback protocol extracted.
"Extensive context has become the norm as Large Language Models (LLMs) are increasingly deployed in long-horizon tasks."
Automatic Metrics
Includes extracted eval setup.
"Extensive context has become the norm as Large Language Models (LLMs) are increasingly deployed in long-horizon tasks."
Not reported
No explicit QC controls found.
"Extensive context has become the norm as Large Language Models (LLMs) are increasingly deployed in long-horizon tasks."
Not extracted
No benchmark anchors detected.
"Extensive context has become the norm as Large Language Models (LLMs) are increasingly deployed in long-horizon tasks."
Context length
Useful for evaluation criteria comparison.
"The concern that increasing context length degrades model capabilities, known as context rot, has become a central issue for these applications."
No benchmark or dataset names were extracted from the available abstract.
Extensive context has become the norm as Large Language Models (LLMs) are increasingly deployed in long-horizon tasks.
Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.
Human feedback protocol is explicit
No explicit human feedback protocol detected.
Evaluation mode is explicit
Detected: Automatic Metrics
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
Detected: context length