Human Feedback Types
missingNone explicit
No explicit feedback protocol extracted.
"Large language models sometimes reply in an unexpected language, a failure known as language confusion."
HFEPX · Eval paper review
Jiwon Jeong, Anjelo Jann Laroza, Chaewoon Yoon, Arjun Pillai +3 more
Published
Oct 18, 2026
Citations
0
Trust level
Low
Usefulness score
0/100 (Low)
Extraction confidence
25% (Low)
Derived from extracted protocol signals and abstract evidence.
Rater population
Not reported
Signals refreshed
Oct 18, 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.
All signals on this page are inferred from the abstract only and may be inaccurate. Do not use this page as a primary protocol reference.
Best use
Background context only
Use if you need
Background context only.
What to verify
Validate the evaluation procedure and quality controls in the full paper before operational use.
Main weakness
This paper looks adjacent to evaluation work, but not like a strong protocol reference.
Treat as adjacent context, not a core eval-method reference.
If you are doing eval pipeline work, start here
Large language models sometimes reply in an unexpected language, a failure known as language confusion. We ablate individual attention heads in 12 model checkpoints spanning seven model series, using FLORES-200 continuations in five languages and Language Confusion Benchmark (LCB) chat replies. In ten models, zeroing one head causes substantially more departures from the expected language than zeroing any other head in its layer; its LCB pass-rate drop persists, though reduced, under mean ablation. Seven heads move 8.0 to 51.5 percent of all FLORES continuations out of the prompt's language, versus at most 1.4 percent for other same-layer heads; the other three mainly affect explicitly requested languages. These seven heads matter less in base models given plain text. In two models, replacing the values a head reads at the requested-language name with another language's mean makes replies fail and shifts some into that language, unlike a random change of equal size. Replacing a head's output with another language's mean redirects 84 to 99 percent of scored non-English monolingual LCB replies into that language in five models. Yet the requested language's mean improves crosslingual replies beyond every control head only in the two Gemma models, whose baselines are low. Code and results are available in the public repository at https://github.com/christian-hoang-04/anonymous-release.
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.
"Large language models sometimes reply in an unexpected language, a failure known as language confusion."
None explicit
Validate eval design from full paper text.
"Large language models sometimes reply in an unexpected language, a failure known as language confusion."
Not reported
No explicit QC controls found.
"Large language models sometimes reply in an unexpected language, a failure known as language confusion."
DROP
Useful for quick benchmark comparison.
"In ten models, zeroing one head causes substantially more departures from the expected language than zeroing any other head in its layer; its LCB pass-rate drop persists, though reduced, under mean ablation."
Not extracted
No metric anchors detected.
"Large language models sometimes reply in an unexpected language, a failure known as language confusion."
No metric terms were extracted from the available abstract.
Large language models sometimes reply in an unexpected language, a failure known as language confusion.
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
No clear evaluation mode extracted.
Quality control reporting appears
No calibration/adjudication/IAA control explicitly detected.
Benchmark or dataset anchors are present
Detected: DROP
Metric reporting is present
No metric terms extracted.