Data as of October 29, 2026 · How the score is built
Released Jun 18, 202632K context
LFM2.5-ColBERT-350M
Decision readingLFM2.5-ColBERT-350M is tracked, but not publicly ranked yet. The profile exposes 2 sourced benchmark rows and leaves unsupported fields blank until a published record exists.
Released Jun 18, 2026 — see all recent releases
Decision snapshot
Each value carries a field reference instead of floating alone. Markers compare this model with the current ranked and priced catalog; they are not absolute quality thresholds.
Capability
Unranked
field median 50.5Not eligible for a public rank
Price
Self-hosted; infrastructure cost varies
input median $0.75No comparable first-party hosted token rate
Speed
Not measured
field median 92 tok/sTime to first token not measured
Context
32Ktokens
field median 256,000Reported for this model; direct source link not stored
Strongest published evidence
Published rows are visible, but no category has enough eligible evidence for a comparative rank.
Validate before choosing
2 published rows leave some tracked benchmark slots empty. No comparable first-party API token rate is published.
Source-linked · 2 displayable benchmark rows
Category score record
Scores and ranks appear only where published evidence can be displayed. The table keeps the score, weight, cohort, and evidence state together.
| Category | Score | Rank | Percentile | Weight | Benchmarks | Evidence |
|---|---|---|---|---|---|---|
| AgenticWeight 22%0 benchmarksNot measured | Not measured | 0 benchmarks | Not measured | |||
| CodingWeight 20%0 benchmarksNot measured | Not measured | 0 benchmarks | Not measured | |||
| ReasoningWeight 17%0 benchmarksNot measured | Not measured | 0 benchmarks | Not measured | |||
| MultimodalWeight 12%0 benchmarksNot measured | Not measured | 0 benchmarks | Not measured | |||
| KnowledgeWeight 12%0 benchmarksNot measured | Not measured | 0 benchmarks | Not measured | |||
| MultilingualWeight 7%2 benchmarksVerified | Score pending | 2 benchmarks | Verified | |||
| Inst. FollowingWeight 5%0 benchmarksNot measured | Not measured | 0 benchmarks | Not measured | |||
| MathWeight 5%0 benchmarksNot measured | Not measured | 0 benchmarks | Not measured |
2 of 782 tracked benchmark slots have displayable evidence · bars run 0–100
Coverage detailsHow much of this is verified
Coverage is split by category so a strong number never hides a thin evidence base. Verified means the row is tied to a published source; provisional rows remain visible but separate.
- AgenticNot measured
- CodingNot measured
- ReasoningNot measured
- MultimodalNot measured
- KnowledgeNot measured
- Multilingual2/2 verified
- Inst. FollowingNot measured
- MathNot measured
Benchmark ledger
Multilingual opens by default. The marker compares each value with the best source-verified result in the catalog; provisional leaders do not set the reference. Expand the remaining categories for every published row.
Multilingual2 rows
| Benchmark | Score | Versus best verified row | Gap | Weight | Evidence |
|---|---|---|---|---|---|
| NanoBEIR MultilingualNanoBEIR Multilingual Extended | Score60.5% | Versus best verified row Best verified: LFM2.5-ColBERT-350M · 60.5% | GapBest verified | WeightDisplay only | Provider exact |
| MKQA-11MKQA-11 multilingual retrieval | Score69.4% | Versus best verified row Best verified: LFM2.5-ColBERT-350M · 69.4% | GapBest verified | WeightDisplay only | Provider exact |
Bars run 0–100; the dark tick marks the best source-verified value
All 2 rowsLineage
The sequence follows explicit supersedes links. Each score is estimated for that model; a relative can inform a sparse estimate but never sets a floor, so a newer release can score below an earlier one. Scores and prices remain blank when the corresponding public row or first-party rate is unavailable.
Spec sheet
Each documented value carries its source. Missing fields stay visible as not sourced or not published, rather than disappearing from the page.
- API model ID
- Not published
- Context window
- 32K
- Maximum output
- Not sourced yet
- Knowledge cutoff
- Not sourced yet
- Input modalities
- Not sourced yet
- Output modalities
- Not sourced yet
- Parameters
- Not sourced yet
- Availability
- Not sourced yet
- Cloud regions
- Not tracked yet
- Lifecycle
- Current
- API capabilities
- Tool calling, structured outputs, and batch support are not tracked yet
- Prompt caching
- Not documented in the pricing record
- Self-host
- Open weights available; hardware estimate not sourced
- Rate limits
- Not tracked yet
How to read this profile
The visual layer above carries the decisions. These notes preserve the model, ranking, coverage, and family context behind the numbers.
We track LFM2.5-ColBERT-350M, but the public leaderboard excludes this profile until enough non-generated benchmark coverage is available. Only published rows appear above.
LFM2.5-ColBERT-350M is a open weight model with a 32K context window. No explicit reasoning mode is documented in this profile.
Official exact-value snapshot from Liquid AI's June 18, 2026 LFM2.5 Retrievers launch post and matching Hugging Face model cards. BenchLM stores the NanoBEIR Multilingual Extended NDCG@10 and MKQA-11 Recall@20 averages as display-only multilingual retrieval rows because these models are retrievers/embedding models, not general chat LLMs.
LFM2.5-ColBERT-350M sits in the LFM2.5 Retrievers family with LFM2.5-Embedding-350M. 2 of 782 tracked benchmark slots currently have displayable evidence. Missing categories stay blank.
Last updated October 29, 2026. Runtime fields remain blank until a sourced snapshot exists.
Deployment options
Self-host and provider-specific paths stay separate from benchmark evidence so operating constraints are visible before a score becomes the whole decision.
Published weights are available, but BenchLM does not yet have a sourced parameter and VRAM profile for this exact model. Hardware cost estimates stay unavailable until that sizing record is complete.
Estimate VRAM from known parametersQuestions
How does LFM2.5-ColBERT-350M perform overall in AI benchmarks?
LFM2.5-ColBERT-350M has 2 source-displayable benchmark rows, but it does not qualify for a public overall rank. The available rows remain visible by category without being converted into a site-wide score. Missing evidence stays blank instead of being estimated from an earlier model.
Is LFM2.5-ColBERT-350M good for multilingual tasks?
LFM2.5-ColBERT-350M has source-displayable benchmark coverage for multilingual tasks, but the public category table does not assign it a rank there. The individual rows remain available for inspection. A missing category position means the evidence threshold was not met; it does not convert the model's unmeasured work into a zero.
Is LFM2.5-ColBERT-350M open source?
LFM2.5-ColBERT-350M is an open-weight model from LiquidAI. Its weights can be downloaded for local or hosted deployment, subject to the published license. Open weight does not automatically mean open source: training data and training code may remain private, and commercial restrictions can still apply.
Which sibling models are related to LFM2.5-ColBERT-350M?
LFM2.5-ColBERT-350M belongs to the LFM2.5 Retrievers family. Related tracked variants include LFM2.5-Embedding-350M. A sibling link indicates shared lineage or a documented configuration relationship; it does not mean the variants have identical pricing, context limits, benchmark evidence, or deployment behavior. Compare before switching.
Does LFM2.5-ColBERT-350M have full benchmark coverage on BenchLM?
No. LFM2.5-ColBERT-350M currently has 2 source-displayable rows. The profile exposes published, non-generated evidence and leaves missing categories blank until an exact evaluation is available. Coverage describes how much was measured; it is not a penalty added to an individual benchmark result.
What is the context window size of LFM2.5-ColBERT-350M?
LFM2.5-ColBERT-350M has a reported context window of 32K in the exact-model catalog record. The value stays visible, but the profile marks its source link as unavailable instead of presenting it as directly documented. Maximum output length remains separate because providers often publish a different limit.