bge-multilingual-gemma2
by BAAI
LLM-based multilingual text embedding — strong cross-lingual retrieval across 100+ languages
BAAI/bge-multilingual-gemma2Overview
BGE-Multilingual-Gemma2 is an embedding model built on the Gemma 2 decoder, trained with contrastive learning over a broad multilingual and cross-lingual corpus. Unlike encoder-only embedders, it inherits the wide language coverage and instruction-following of an LLM backbone, which makes it a common default when a corpus spans many languages or when queries and documents are in different languages.
On Mixpeek, BGE-Multilingual-Gemma2 is a text embedding extractor for multilingual document and metadata search. It pairs well with a reranker for precision and with a multimodal encoder when text is only one of several modalities an agent must search.
Architecture
Decoder-based (Gemma 2 9B) embedding model. The final hidden state is pooled into a dense sentence embedding and trained with contrastive (InfoNCE) loss over multilingual query-document pairs, including cross-lingual positives so a query in one language retrieves documents in another.
Key Capabilities
- •Dense text embeddings across 100+ languages
- •Strong cross-lingual retrieval (query and document in different languages)
- •Instruction-aware query encoding inherited from the LLM backbone
- •Long-context passages for document-level retrieval
Use Cases on Mixpeek
- •Multilingual document and metadata search over a global content library
- •Cross-lingual retrieval where an English query must surface non-English documents
- •Agent perception over international support tickets, contracts, or transcripts
- •First-stage recall feeding a reranker for precision
Tags
Use bge-multilingual-gemma2 on Mixpeek
Build multimodal processing pipelines with this model and others. Extract features, run inference, and set up retrieval in Mixpeek Studio.
Open StudioHow It Runs on Mixpeek
On Mixpeek, bge-multilingual-gemma2 runs as a managed extractor inside a processing pipeline. Point a bucket of feature extraction data at it, and Mixpeek handles GPU provisioning, batching, retries, and writing the outputs into a vector store you can query.
Extractor outputs land in the Mixpeek Vector Store (MVS), where you can combine them with retrieval, reranking, and filter stages to build end-to-end search and agent-perception pipelines, no model-serving infrastructure to maintain.
Explore on Mixpeek
Compare alternatives in this category
Hand-picked tools & platforms compared
Deep-dive technical guide
See how Mixpeek runs models as extractors
Store & search embeddings at scale
Usage-based pricing for pipelines
Compare models, APIs & infrastructure
Specification
View on HuggingFace
See model card, files, and community discussion