Home / Companies / Hugging Face / Blog / Post Details
Content Deep Dive

mLateOn: A New SoTA for Multilingual ColBERT-Style Retrieval, Evaluated on HAKARI-Bench

Blog post from Hugging Face

Post Details
Company
Date Published
Author
Yuichi Tateno
Word Count
5,061
Company Posts That Month
74
Language
-
Hacker News Points
-
Post removed?
No
Summary

mLateOn, LightOn’s multilingual ColBERT-style late-interaction retrieval model, achieved the highest HAKARI-Bench Overall score among 11 evaluated late-interaction models, scoring 65.52 Macro with 115.1 million active parameters and support for inputs up to 8,192 tokens. On MNanoBEIR, it scored 63.33, placing between Qwen3-Embedding-8B and Nemotron-3-Embed-8B despite using far fewer active parameters, although the comparison concerns retrieval quality rather than indexing, latency, memory, or system cost. The model performed above the peer average across all 14 evaluated languages, showed particular strength on multilingual BEIR-style and long-document retrieval, and remained competitive with leading English-only ColBERT systems on English tasks. Its reusable document token vectors also enabled competitive fixed-candidate reranking, particularly for short queries, where it outperformed several dedicated pair rerankers in the benchmark. Results were weaker on longer-query tasks and some domains such as code retrieval, and performance on MLDR-related long-document tasks requires caution because LightOn disclosed training overlap. The article’s author, who created and maintains HAKARI-Bench, explicitly disclosed this role and emphasized that deployment decisions should additionally evaluate multi-vector indexing requirements, corpus-specific effectiveness, and operational costs.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Vector Search 34 2,312 357 123 +3%
AI Model Fine-tuning 4 516 143 56 -47%
LLM 2 4,718 960 222 -38%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.