Multilingual Question Answering (MLQA) is a benchmark dataset designed to evaluate cross-lingual question answering systems, where a question posed in English must be answered by extracting an answer span from a context passage written in one of seven target languages. It specifically tests a model's capacity for zero-shot cross-lingual transfer, requiring the system to bridge the semantic gap between the English query and the foreign-language evidence without explicit translation.
Glossary
Multilingual Question Answering (MLQA)

What is Multilingual Question Answering (MLQA)?
A rigorous benchmark for evaluating a model's ability to answer questions across language boundaries, where the question is in English but the supporting context is in a different language.
The MLQA dataset contains over 12,000 extractive question-answer instances across English, Arabic, German, Spanish, Hindi, Vietnamese, and Simplified Chinese. Unlike translation-based approaches, it forces models to develop language-agnostic representations by aligning English questions with answer spans in the target language's context, making it a critical standard for evaluating architectures like XLM-RoBERTa and mBERT in production multilingual search systems.
Frequently Asked Questions
Explore the core concepts behind Multilingual Question Answering (MLQA), a critical benchmark for evaluating how AI systems transfer knowledge across language boundaries to find answers in foreign-language contexts.
The Multilingual Question Answering (MLQA) benchmark is a cross-lingual evaluation dataset designed to measure a model's ability to answer questions across language boundaries. It operates on a specific cross-lingual transfer setup: all questions and their corresponding answers are provided in English, but the context passages containing the evidence are written in one of seven target languages (Arabic, German, Spanish, Hindi, Vietnamese, Simplified Chinese, or English as a control). The model must locate the correct answer span within the foreign-language passage. This design explicitly tests for language-agnostic semantic understanding, as the model cannot rely on lexical overlap between the English question and the target-language text. The dataset contains over 12,000 instances across the seven languages, built by manually translating and curating passages from the SQuAD dataset to ensure high-quality, parallel evaluation data.
Key Features of the MLQA Dataset
The Multilingual Question Answering (MLQA) dataset is a benchmark designed to evaluate cross-lingual generalization. It forces models to answer English questions using context passages written in one of seven target languages, testing the limits of language-agnostic semantic understanding.
Cross-Lingual Generalization
MLQA evaluates a model's ability to perform zero-shot cross-lingual transfer. The system must learn to answer questions in English and generalize that ability to find answers in passages written in languages it was not fine-tuned on. This tests the true language-agnostic nature of the underlying representations, moving beyond simple translation to semantic understanding.
Dataset Composition and Scale
The benchmark is constructed from parallel corpora, specifically articles from Wikipedia that have been professionally translated. It spans 7 typologically diverse languages:
- Arabic (ar)
- German (de)
- English (en)
- Spanish (es)
- Hindi (hi)
- Vietnamese (vi)
- Simplified Chinese (zh) The dataset contains over 12,000 question-answer instances per language, ensuring statistical significance in evaluation.
The English-Only Question Constraint
A defining characteristic of MLQA is that all questions are formulated in English, regardless of the context language. This design choice isolates the model's cross-lingual reading comprehension capability. It prevents the model from relying on simple lexical overlap or keyword matching between the question and the passage, forcing a deep semantic alignment between the English query and the foreign-language text.
Answer Span Extraction
MLQA is an extractive question answering task. The model must predict the exact start and end character indices of the answer within the target language context passage. This requires precise token-level understanding across different scripts and writing systems, such as Latin, Arabic, Devanagari, and Hanzi. The metric used for evaluation is the standard F1 score and Exact Match (EM).
Typological Diversity
The seven languages were selected to maximize linguistic diversity, challenging models with different syntactic structures and morphological complexities:
- Morphologically Rich: Arabic and Hindi require handling complex inflection and agglutination.
- Analytic/Isolating: Vietnamese and Chinese lack word boundaries and inflection, testing tokenization strategies.
- Synthetic: German and Spanish introduce compounding and grammatical gender agreement. This diversity makes MLQA a robust testbed for multilingual masked language modeling.
Relationship to Other Benchmarks
MLQA complements other cross-lingual benchmarks like XNLI (Cross-Lingual Natural Language Inference) and TyDi QA. While XNLI tests sentence-level reasoning and TyDi QA focuses on typologically diverse languages with native questions, MLQA specifically targets cross-lingual transfer in reading comprehension with a fixed English question set. It is a standard evaluation for models like XLM-RoBERTa and mBERT.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
MLQA vs. Other Multilingual QA Benchmarks
A feature-level comparison of the MLQA dataset against XNLI and TyDi QA for evaluating cross-lingual question answering systems.
| Feature | MLQA | XNLI | TyDi QA |
|---|---|---|---|
Primary Task | Extractive QA | Natural Language Inference | Passage QA |
Cross-Lingual Transfer | |||
Number of Languages | 7 | 15 | 11 |
Parallel Evaluation Data | |||
Typologically Diverse Languages | |||
Zero-Shot Evaluation Setting | |||
Answer Span Annotation | |||
Context Language Mismatch |
Related Terms
Core concepts and benchmarks that define the landscape of multilingual question answering and cross-lingual evaluation.
Cross-Lingual Transfer
The foundational technique enabling MLQA evaluation. A model is fine-tuned on a high-resource source language (e.g., English QA data) and evaluated on its ability to answer questions about passages in a target language without any target-language training data. This tests the model's ability to learn language-agnostic reasoning. Success depends on the quality of the shared multilingual representation space.
Cross-Lingual Natural Language Inference (XNLI)
A benchmark for evaluating cross-lingual sentence understanding. The task is to determine if a hypothesis in one language is entailed by, contradicts, or is neutral to a premise in another. XNLI is a critical test of a model's ability to capture logical relationships across language boundaries, a skill directly transferable to verifying answer validity in MLQA systems.
Language-Agnostic Sentence Representations
The underlying technology that makes MLQA possible. Models like LaBSE and LASER encode sentences from different languages into a shared vector space where semantically identical sentences map to the same region. This alignment allows a question in English to be compared directly with a passage in Arabic or Hindi using cosine similarity.
Cross-Lingual Re-Ranking
A two-stage retrieval pipeline critical for production MLQA systems. A fast multilingual retriever (e.g., mDPR) first fetches candidate passages from a target language corpus. A more computationally intensive cross-encoder then scores the relevance of each (English query, target-language passage) pair with full cross-attention, significantly improving the precision of the final answer extraction.
XLM-RoBERTa
A strong baseline model for MLQA tasks. Trained on 100 languages using masked language modeling on a massive 2.5TB corpus, XLM-RoBERTa builds robust cross-lingual representations without explicit parallel data. It demonstrates that scale and diversity in pre-training data can overcome the need for direct translation pairs, enabling effective zero-shot transfer to low-resource languages.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us