Monolingual language ID is solved. Mixed-language text is where MixLID's 22-point jump actually happens.

A paper posted 12 October 2026 introduces MixLID, a 111-language token-level identification model, and its own results show the real gap is not where the headline claim points. On four monolingual benchmarks, the strongest baseline already scores up to 99.58% accuracy, leaving MixLID almost nothing to improve. On mixed-language, code-switched text, the best prior baseline scores 71.6% token accuracy on one benchmark, and MixLID reaches 93.23%, a 21.6-point jump.
What the paper is, and what problem it targets
Seongtae Hong, Youngjoon Jang, Seungyoon Lee, Jungseob Lee, and Heuiseok Lim, at Korea University, posted arXiv:2610.16601 on 12 October 2026. Their stated motivation is a gap in multilingual data pipelines: sentence-level language identification (is this document in Spanish?) is a largely solved problem, but token-level identification inside a single utterance that mixes languages (which word, in this sentence, is Spanish and which is English?) is not, and that gap matters directly for anyone building training data for low-resource or code-switching-heavy markets, where real speech routinely mixes languages mid-sentence.
MixLID is a 114-way token classifier (111 language-script labels plus NUM, PUNCT, SYM) built on mmBERT-small, trained in two stages: first on monolingual text to learn each language in isolation, then continuing on mixed-language text built from real code-switching corpora plus a loanword-substitution technique that swaps English source words for borrowed-word equivalents using Wiktionary etymological data, applied with 70% probability per eligible word.
Where the gain is, and where it isn't
Monolingual sentence-level identification, accuracy / macro F1, selected columns from the paper's Table 1 (comparisons are restricted to the language subset each baseline shares with MixLID, so this is not a single number across the board):
| Benchmark | Best prior baseline | Baseline score | MixLID score |
|---|---|---|---|
| FLORES+ | Polyglot | 99.46 / 99.91 | 99.58 / 99.92 (reported best column) |
| WiLI-2018 | Polyglot | 98.58 / 98.84 | 98.88 / 98.92 |
| UDHR | Polyglot | 99.33 / 99.84 | 99.54 / 99.84 |
| CommonLID | fastText | 95.93 / 97.74 | 95.42 / 97.74 (not a win on accuracy) |
Mixed-language, token-level identification, token accuracy / macro F1, from the paper's Table 3:
| Benchmark | CLD3 | MaskLID | Polyglot (best prior) | MixLID |
|---|---|---|---|---|
| ACS | 54.6 / 33.9 | 33.6 / 21.3 | 71.6 / 53.9 | 93.23 / 88.78 |
| CodeMixBench | 74.2 / 51.5 | 47.6 / 25.9 | 85.6 / 64.1 | 94.50 / 87.29 |
The two-stage pipeline, and the loanword trick that builds stage 2's data
The paper's own ablation (its Table 4) shows the two stages trade off: Stage 1 alone is strongest on sentence-level benchmarks, Stage 2 alone is strongest on token-level mixed-language data, and the combined model wins on mixed-language and most sentence-level benchmarks. The paper describes the two stages as having "complementary roles," which is a fair description of a tradeoff, not a free win: training on synthetic loanword-substituted text is what buys the mixed-language gain, and the paper's own limitations section flags that dictionary-based substitution "may not account for contextual usage and linguistic ambiguity," which could introduce unnatural expressions or labeling errors into exactly the training signal responsible for the 21.6-point gain.
What this means for building multilingual training data
For anyone assembling a low-resource or code-switching-heavy localization dataset, the practical takeaway is narrow and specific: sentence-level language tagging tools, which most pipelines already use to filter corpora, are not the bottleneck. They were already at 93 to 99.6% before this paper. The bottleneck is tagging which word, inside an already-mixed sentence, belongs to which language, and that is where a 21.6-point gap existed until this model, on the one benchmark (ACS) the paper reports it against four comparison systems.
The caveat that should travel with any adoption decision: MixLID's language coverage caps at 111 language-script combinations, and the mixed-language training data leans heavily on synthetic substitution for 3 of its 4 sources. A team building data for a language pair outside that list, or evaluating on genuinely spontaneous code-switching rather than substitution-augmented text, should expect the gain to be smaller than the headline 21.6 points until tested directly on their own language pair.
Check it yourself
- The paper: arXiv:2610.16601, "MixLID: Token-Level Language Identification in Mixed-Language Text," posted 12 October 2026.
- Full text with Tables 1, 3, 4 and 5 (the full 111-language list): arxiv.org/html/2610.16601v1.
- OpenLID-v3, the Stage 1 monolingual source: check its own language list against your target languages before assuming coverage.
- Recompute the gap yourself: 93.23 (MixLID, ACS) minus 71.6 (Polyglot, ACS) = 21.63 points. 94.50 (MixLID, CodeMixBench) minus 85.6 (Polyglot, CodeMixBench) = 8.9 points, a smaller gap on the second benchmark, worth noting before treating 21.6 as the number that generalizes.
What would prove this wrong
If a third-party evaluation on genuinely spontaneous (not substitution-augmented) code-switched speech transcripts, across a language pair outside MixLID's 111-combination list, shows the mixed-language gain shrinking to within 5 points of Polyglot before the end of 2027, the 21.6-point result reported here should be read as specific to the ACS benchmark and the substitution-based training recipe, not a general property of the method.
Sources
- Seongtae Hong, Youngjoon Jang, Seungyoon Lee, Jungseob Lee, Heuiseok Lim, "MixLID: Token-Level Language Identification in Mixed-Language Text," arXiv:2610.16601, 12 October 2026.
BLOMEGA pays humans for the data AI needs, consented and rights-cleared. blomega.com