Models & Research

Hugging Face adds ColBERT training in Sentence Transformers v6.0

Hugging Face shipped Sentence Transformers v6.0 on 18 August 2026, adding MultiVectorEncoder as a fourth model type alongside SentenceTransformer, CrossEncoder and SparseEncoder. The release notes call it support for training, inferencing and interpreting ColBERT-style late interaction models.

The mechanism matters, because it’s what the rest of the numbers rest on. A dense model compresses a whole text into one vector, so similarity is a single dot product between two summaries. A multi-vector model keeps one vector per token and scores a query with MaxSim, where each query token finds its best matching document token and the scores are summed. That’s the design Omar Khattab and Matei Zaharia introduced as ColBERT in April 2020, reporting retrieval two orders of magnitude faster than the BERT rankers of the day.

So to show what that buys you, Tom Aarsen published a training walkthrough on Hugging Face’s blog on 26 August that finetunes a medical retriever. He started from lightonai/mLateOn-unsupervised, a contrastively pretrained checkpoint that hasn’t been through supervised finetuning, trained on a million question and passage pairs drawn from the 4.4 million question MIRIAD corpus, and ran it for 14.5 hours on a single RTX 3090 at a peak of 17.5 GB of VRAM. He then evaluated that model on 1,000 held-out questions searching 200,000 passages.

ModelFamilyNDCG@10
multi-vector-encoder/mLateOn-medicalMulti-vector, finetuned0.9139
lightonai/mLateOnMulti-vector, zero-shot0.8520
Qwen/Qwen3-Embedding-4BDense, zero-shot0.7817
BM25Lexical0.7501
naver/splade-v3Sparse, zero-shot0.6853
MIRIAD medical retrieval, 1,000 queries against 200,000 passages. Source: Hugging Face.

The finetuned model beat the strongest zero-shot model of any architecture by 0.062 NDCG@10. Translated into hit rates, that means the best zero-shot model returned the right passage as its very first result for 75.8% of queries, while the finetuned model did so for 84.9%. Aarsen describes the gap as cutting the rank-1 error by more than a third.

But part of that gap isn’t architecture at all, it’s document length. The MIRIAD passages average 941 tokens, and classic ColBERT checkpoints cap documents at 180 or 300 tokens while many dense models stop at 256 or 512. Aarsen measured that truncation costing up to 0.24 NDCG@10 on this data, more than any difference between the model architectures themselves. LightOn’s mLateOn, a 307M parameter multilingual ColBERT model, serves its backbone’s full 8,192 token context instead.

The starting point mattered too, and in a way the write-up admits was a surprise. Across six checkpoints trained with an identical recipe on 25,000 pairs, and scored against a smaller 50,000 passage corpus that isn’t comparable to the table above, the unsupervised mLateOn checkpoint moved from 0.9087 to 0.9398, a gain of 0.0311. Its finished sibling started higher at 0.9277 and crawled to 0.9319, a gain of 0.0042. Pre-supervised checkpoints carry the late interaction structure without the general-purpose tuning that domain finetuning then has to undo.

The objection that multi-vector indexes are too big does not survive a properly configured index.

Tom Aarsen, via Hugging Face

That’s the objection anyone running a vector database raises first, because one vector per token is a lot of vectors. The post answers it with quantization, so the last row of his quantization table lands at 1.45 GB, smaller than the fp16 embeddings of Qwen3-Embedding-8B at 1.64 GB, while scoring 0.0895 higher. A punctuation skiplist trimmed another 9.6% off the index for free.

What that leaves is a cost question rather than a capability one, though it’s cheaper than the 14.5-hour run suggests. Aarsen’s scaling experiments put 100,000 pairs, which is 75 minutes of training, within 0.012 NDCG@10 of the full million-pair result. Most of the gain arrives in the first hour. If your domain data looks anything like this, the thing to watch is whether teams start treating a domain retriever as a routine build rather than a vendor decision, and whether the RAG stacks already in production bother to re-measure their truncation limits.

Get the daily rundown

One email each weekday with the AI news that matters, every claim linked to its primary source.

Free, one email each weekday, unsubscribe in one click. We never sell or share your address.

Leave a Reply

Your email address will not be published. Required fields are marked *