Skip to content
OpenTrain AIFor AI Companies

HFEPX · Eval paper review

Can We Make an LLM Dumber, or Is It Just Playing Dumb? An Empirical Study of Believable Performance Throttling

Chengguang Gan, Yunhao Liang, Hanjun Wei, QingHao Zhang +1 more

Published

Nov 11, 2026

Citations

0

Trust level

Moderate

Usefulness score

35/100 (Low)

Extraction confidence

55% (Moderate)

Derived from extracted protocol signals and abstract evidence.

Rater population

Not reported

Signals refreshed

Nov 11, 2026

Should you rely on this paper?

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.

Best use

Background context only

Use if you need

A secondary eval reference to pair with stronger protocol papers.

What to verify

Validate the exact study setup in the full paper before operational use.

Main weakness

No major weakness surfaced.

Human feedback signal
Not explicit
Not explicit in abstract metadata
Evaluation signal
Detected
Eval setup described
Usefulness for eval research
35/100
Adjacent candidate

Treat as adjacent context, not a core eval-method reference.

Abstract

A benchmark score is commonly read as a proxy for model capability. We study the inverse problem: can a model be driven to a target score, and do its failures resemble those of a naturally weaker model? We operationalize believable performance reduction along three axes: target calibration, item-difficulty structure, and error-distribution similarity to a real weak reference. We introduce CapLadder, an IRT-calibrated suite of 1,985 items spanning mathematics, code, multiple-choice reasoning, and tool use. A simple weak-teacher LoRA dial reaches unseen target levels on reasoning with a 1.9-point held-out calibration error, whereas prompting, temperature, and weight noise cannot combine comparable range and precision. Yet on multiple choice, the dial converges to an answer-token attractor: up to 97% of its newly introduced errors land on one letter, with the attractor changing from D in Qwen to A in Llama. Logit interventions identify a dominant near-constant shift: subtracting the estimated shift on held-out items recovers 52 to 59% of lost accuracy and removes the dominant attractor, while option permutation confirms that the bias tracks token position rather than option content. With high inter-annotator agreement ($κ=0.94$), human-coded error-category distributions nonetheless match the weak reference on reasoning (JS = 0.00), showing that local plausibility and aggregate detectability differ. Structured tool calls exhibit more natural degradation in the Qwen family (JS = 0.09), while a globally calibrated dial transfers poorly across benchmarks (14.2-point error on two usable benchmarks). Precise score control, therefore, does not imply a portable or believable reduction in skill.

What we could verify

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.

Human Feedback Types

missing

None explicit

No explicit feedback protocol extracted.

"A benchmark score is commonly read as a proxy for model capability."

Evaluation Modes

strong

Automatic Metrics

Includes extracted eval setup.

"A benchmark score is commonly read as a proxy for model capability."

Quality Controls

strong

Inter Annotator Agreement Reported

Calibration/adjudication style controls detected.

"A benchmark score is commonly read as a proxy for model capability."

Benchmarks / Datasets

missing

Not extracted

No benchmark anchors detected.

"A benchmark score is commonly read as a proxy for model capability."

Reported Metrics

strong

Accuracy, Agreement

Useful for evaluation criteria comparison.

"Logit interventions identify a dominant near-constant shift: subtracting the estimated shift on held-out items recovers 52 to 59% of lost accuracy and removes the dominant attractor, while option permutation confirms that the bias tracks token position rather than option content."

Benchmarks and datasets

No benchmark or dataset names were extracted from the available abstract.

Reported metrics

accuracyagreement
Human feedback details
Uses human feedback
No
Feedback types
None
Rater population
Not reported
Expertise required
Math, Coding
Evaluation details
Evaluation modes
Automatic Metrics
Agentic eval
Tool Use
Quality controls
Inter Annotator Agreement Reported
Evidence quality
Moderate
Use this page as
Background context only

Research brief

Metadata summary

A benchmark score is commonly read as a proxy for model capability.

Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.

Key takeaways

  • A benchmark score is commonly read as a proxy for model capability.
  • We study the inverse problem: can a model be driven to a target score, and do its failures resemble those of a naturally weaker model?
  • We operationalize believable performance reduction along three axes: target calibration, item-difficulty structure, and error-distribution similarity to a real weak reference.

Researcher actions

  • Compare this paper against nearby papers in the same arXiv category before using it for protocol decisions.
  • Validate inferred eval signals (Automatic metrics, Tool-use evaluation) against the full paper.
  • Use related-paper links to find stronger protocol-specific references.

Caveats

  • Generated from abstract + metadata only; no PDF parsing.
  • Signals below are heuristic and may miss details reported outside the abstract.

Contribution summary

  • A benchmark score is commonly read as a proxy for model capability.
  • We study the inverse problem: can a model be driven to a target score, and do its failures resemble those of a naturally weaker model?

Why it matters for eval

  • Structured tool calls exhibit more natural degradation in the Qwen family (JS = 0.09), while a globally calibrated dial transfers poorly across benchmarks (14.2-point error on two usable benchmarks).

Researcher checklist

  • Human feedback protocol is explicit

    No explicit human feedback protocol detected.

  • Evaluation mode is explicit

    Detected: Automatic Metrics

  • Quality control reporting appears

    Detected: Inter Annotator Agreement Reported

  • Benchmark or dataset anchors are present

    No benchmark/dataset anchor extracted from abstract.

  • Metric reporting is present

    Detected: accuracy, agreement