Model reference · open weights

Linq-Embed-Mistral

Embeddings Linq-AI-Research Embeddings 1 build Non-commercial 16k dl/mo

Linq-Embed-Mistral is an open-weight embedding model from Linq-AI-Research. Linq-Embed-Mistral (FP16) weighs 14.2 GB; the smallest configuration that runs it is RTX 4060 Ti 16 GB.

  • Linq-Embed-Mistral is a 7.1B parameter feature-extraction model developed by Linq-AI-Research for text retrieval tasks.
  • It supports a context length of 32,768 tokens and is licensed under cc-by-nc-4.0.
  • The model is designed for English language processing and achieves a retrieval score of 60.2 on the MTEB benchmark.

Summary of the Linq-AI-Research/Linq-Embed-Mistral model card, 2026-10-01

What it is

Released byLinq-AI-Research
Released2024-05-29
Parameters7.1B
VRAM14.2 GB for the weights

What it runs on

Memory and cards for Linq-Embed-Mistral (FP16)

14.2 GBweights, file size
1.1 GBruntime overhead
CardRunsMemory
RTX 3060 12 GBdoes not fit11.6 GB
RTX 4060 Ti 16 GBtight15.4 GB
RTX 3090 24 GBfits23.4 GB
RTX 4090 24 GBfits23.4 GB
RTX 5090 32 GBfits31.0 GB
L40S 48 GBfits44.0 GB
A100 80 GBfits78.2 GB
H100 80 GBfits78.1 GB
RTX PRO 6000 Blackwell 96 GBfits93.8 GB
DGX Spark (GB10) 128 GB unifiedfits107 GB
H200 141 GBfits138 GB
B200 180 GBfits176 GB

From the model card

What Linq-AI-Research says about Linq-Embed-Mistral

Read the model card

Linq-Embed-Mistral

Linq-Embed-Mistral has been developed by building upon the foundations of the E5-mistral-7b-instruct and Mistral-7B-v0.1 models. We focus on improving text retrieval using advanced data refinement methods, including sophisticated data crafting, data filtering, and negative mining guided by teacher models, which are highly tailored to each task, to improve the quality of the synthetic data generated by LLM. These methods are applied to both existing benchmark dataset and highly tailored synthetic dataset generated via LLMs. Our efforts primarily aim to create high-quality triplet datasets (query, positive example, negative example), significantly improving text retrieval performance.

Linq-Embed-Mistral performs well in the MTEB benchmarks (as of May 29, 2024). The model excels in retrieval tasks, ranking 1st among all models listed on the MTEB leaderboard with a performance score of 60.2. This outstanding performance underscores its superior capability in enhancing search precision and reliability. The model achieves an average score of 68.2 across 56 datasets in the MTEB benchmarks, making it the highest-ranking publicly accessible model and third overall. (Please note that NV-Emb-v1 and voyage-large-2-instruct, ranked 1st and 2nd on the leaderboard as of May 29, reported their performance without releasing their models.)

This project is for research purposes only. Third-party datasets may be subject to additional terms and conditions under their associated licenses. Please refer to specific papers for more details:

For more details, refer to this blog post and this report.

How to use

Here is an example of how to encode queries and passages from the Mr.TyDi training dataset, both with Sentence Transformers or Transformers directly.

Sentence Transformers

from sentence_transformers import SentenceTransformer

# Load the model
model = SentenceTransformer("Linq-AI-Research/Linq-Embed-Mistral")

# Each query must come with a one-sentence instruction that describes the task
task = 'Given a question, retrieve Wikipedia passages that answer the question'
prompt = f"Instruct: {task}\nQuery: "
queries = [
    "최초의 원자력 발전소는 무엇인가?",
    "Who invented Hangul?"
]
passages = [
    "현재 사용되는 핵분열 방식을 이용한 전력생산은 1948년 9월 미국 테네시주 오크리지에 설치된 X-10 흑연원자로에서 전구의 불을 밝히는 데 사용되면서 시작되었다. 그리고 1954년 6월에 구소련의 오브닌스크에 건설된 흑연감속 비등경수 압력관형 원자로를 사용한 오브닌스크 원자력 발전소가 시험적으로 전력생산을 시작하였고, 최초의 상업용 원자력 엉더이로를 사용한 영국 셀라필드 원자력 단지에 위치한 콜더 홀(Calder Hall) 원자력 발전소로, 1956년 10월 17일 상업 운전을 시작하였다.",
    "Hangul was personally created and promulgated by the fourth king of the Joseon dynasty, Sejong the Great.[1][2] Sejong's scholarly institute, the Hall of Worthies, is often credited with the work, and at least one of its scholars was heavily involved in its creation, but it appears to have also been a personal project of Sejong."
]

# Encode the queries and passages. We only use the prompt for the queries
query_embeddings = model.encode(queries, prompt=prompt)
passage_embeddings = model.encode(passages)

# Compute the (cosine) similarity scores
scores = model.similarity(query_embeddings, passage_embeddings) * 100
print(scores.tolist())
# [[73.72908782958984, 30.122787475585938], [29.15508460998535, 79.25375366210938]]

Transformers

import torch
import torch.nn.functional as F
from torch import Tensor
from transformers import AutoTokenizer, AutoModel

def last_token_pool(last_hidden_states: Tensor,
                 attention_mask: Tensor) -> Tensor:
    left_padding = (attention_mask[:, -1].sum() == attention_mask.shape[0])
    if left_padding:
        return last_hidden_states[:, -1]
    else:
        sequence_lengths = attention_mask.sum(dim=1) - 1
        batch_size = last_hidden_states.shape[0]
        return last_hidden_states[torch.arange(batch_size, device=last_hidden_states.device), sequence_lengths]

def get_detailed_instruct(task_description: str, query: str) -> str:
    return f'Instruct: {task_description}\nQuery: {query}'

# Each query must come with a one-sentence instruction that describes the task
task = 'Given a question, retrieve Wikipedia passages that answer the question'
queries = [
    get_detailed_instruct(task, '최초의 원자력 발전소는 무엇인가?'),
    get_detailed_instruct(task, 'Who invented Hangul?')
]
# No need to add instruction for retrieval documents
passages = [
    "현재 사용되는 핵분열 방식을 이용한 전력생산은 1948년 9월 미국 테네시주 오크리지에 설치된 X-10 흑연원자로에서 전구의 불을 밝히는 데 사용되면서 시작되었다. 그리고 1954년 6월에 구소련의 오브닌스크에 건설된 흑연감속 비등경수 압력관형 원자로를 사용한 오브닌스크 원자력 발전소가 시험적으로 전력생산을 시작하였고, 최초의 상업용 원자력 엉더이로를 사용한 영국 셀라필드 원자력 단지에 위치한 콜더 홀(Calder Hall) 원자력 발전소로, 1956년 10월 17일 상업 운전을 시작하였다.",
    "Hangul was personally created and promulgated by the fourth king of the Joseon dynasty, Sejong the Great.[1][2] Sejong's scholarly institute, the Hall of Worthies, is often credited with the work, and at least one of its scholars was heavily involved in its creation, but it appears to have also been a personal project of Sejong."
]

# Load model and tokenizer
tokenizer = AutoTokenizer.from_pretrained('Linq-AI-Research/Linq-Embed-Mistral')
model = AutoModel.from_pretrained('Linq-AI-Research/Linq-Embed-Mistral')

max_length = 4096
input_texts = [*queries, *passages]
# Tokenize the input texts
batch_dict = tokenizer(input_texts, max_length=max_length, padding=True, truncation=True, return_tensors="pt")
outputs = model(**batch_dict)
embeddings = last_token_pool(outputs.last_hidden_state, batch_d

Quoted from the model card on Hugging Face. The full card is behind the Hugging Face link above.

Benchmarks

Reported results

As published on the model card: the maker's own numbers, not measured by AxForge.

TaskDatasetMetricScore
ClassificationMTEB AmazonCounterfactualClassification (en)accuracy84.433
ClassificationMTEB AmazonCounterfactualClassification (en)ap50.392
ClassificationMTEB AmazonCounterfactualClassification (en)f178.479
ClassificationMTEB AmazonPolarityClassificationaccuracy95.704
ClassificationMTEB AmazonPolarityClassificationap94.283
ClassificationMTEB AmazonPolarityClassificationf195.700
ClassificationMTEB AmazonReviewsClassification (en)accuracy57.644
ClassificationMTEB AmazonReviewsClassification (en)f156.994
RetrievalMTEB ArguAnamap_at_145.804
RetrievalMTEB ArguAnamap_at_1061.742
RetrievalMTEB ArguAnamap_at_10062.079
RetrievalMTEB ArguAnamap_at_100062.080
RetrievalMTEB ArguAnamap_at_357.717
RetrievalMTEB ArguAnamap_at_560.270
RetrievalMTEB ArguAnamrr_at_147.226
RetrievalMTEB ArguAnamrr_at_1062.256
RetrievalMTEB ArguAnamrr_at_10062.601
RetrievalMTEB ArguAnamrr_at_100062.601
RetrievalMTEB ArguAnamrr_at_358.203
RetrievalMTEB ArguAnamrr_at_560.767
RetrievalMTEB ArguAnandcg_at_145.804
RetrievalMTEB ArguAnandcg_at_1069.649
RetrievalMTEB ArguAnandcg_at_10070.902
RetrievalMTEB ArguAnandcg_at_100070.912
© 2026 AxForge · EU-hosted AI infrastructure Pricing Docs Trust Privacy Terms