The FEVER Dataset is a publicly available benchmark containing 185,445 claims generated by human annotators, each mapped to a Wikipedia dump. Its core task requires a model to retrieve relevant evidence and classify a claim as Supported, Refuted, or NotEnoughInfo, making it a standard for training and evaluating evidence-based fact verification systems.
Glossary
FEVER Dataset

What is FEVER Dataset?
The Fact Extraction and VERification (FEVER) dataset is a large-scale benchmark for evaluating automated fact-checking systems against Wikipedia.
Introduced to advance automated fact-checking, FEVER demands joint Natural Language Inference (NLI) and evidence retrieval capabilities. The dataset's structured three-label classification and granular evidence annotation enable rigorous testing of a model's ability to perform textual entailment and avoid hallucination when verifying real-world assertions against a closed corpus.
Key Features of the FEVER Dataset
The Fact Extraction and VERification (FEVER) dataset is a large-scale benchmark for evidence-based claim verification. It pairs 185,445 human-generated claims with Wikipedia evidence, requiring models to retrieve relevant passages and predict whether a claim is Supported, Refuted, or NotEnoughInfo.
Three-Way Veracity Classification
FEVER defines a strict ternary label space that forces models to distinguish between definitive truth, definitive falsehood, and epistemic uncertainty.
- SUPPORTS: The retrieved evidence confirms the claim is true.
- REFUTES: The retrieved evidence confirms the claim is false.
- NOT ENOUGH INFO: Wikipedia does not contain sufficient information to verify or refute the claim.
This tripartite structure prevents models from guessing when evidence is absent, a critical requirement for real-world fact-checking systems where silence is preferable to hallucination.
Evidence-Based Pipeline Task
FEVER is not a single classification task but a composite pipeline requiring two distinct stages:
- Document Retrieval: Models must first search Wikipedia to find relevant documents, simulating real-world information-seeking behavior.
- Textual Entailment: Given retrieved sentences, models perform Natural Language Inference to determine if the evidence logically entails or contradicts the claim.
This decomposition mirrors production fact-checking architectures where retrieval and verification are separate, evaluable components. The dataset provides gold-standard evidence annotations for supervised training of both stages.
Human-Generated Claim Construction
Claims in FEVER were created by human annotators who were instructed to mutate sentences from Wikipedia into factual assertions, ensuring natural linguistic diversity.
- Annotators rephrased, negated, or generalized original sentences to produce claims that sound like real-world statements.
- This process avoids the artificiality of template-generated claims and introduces genuine lexical variation, negation patterns, and syntactic complexity.
- Claims cover a broad range of topics including history, science, entertainment, and geography, testing domain generalization.
The human-in-the-loop design ensures that models trained on FEVER encounter the same ambiguities and phrasing variations present in actual misinformation.
Strict Annotator Agreement Protocol
FEVER employed a rigorous multi-annotator validation process to ensure label quality and minimize subjective bias in veracity judgments.
- Each claim was independently labeled by multiple annotators.
- Claims with disagreement were adjudicated or discarded, resulting in high inter-annotator agreement.
- The final dataset achieved a Fleiss' Kappa score indicating near-perfect agreement on the SUPPORTS/REFUTES/NOTENOUGHINFO distinction.
This methodological rigor makes FEVER a trusted benchmark where evaluation metrics reflect genuine model capability rather than annotation noise, a common pitfall in crowdsourced NLP datasets.
FEVER Score Evaluation Metric
The official evaluation metric, the FEVER Score, jointly measures both evidence retrieval quality and veracity prediction accuracy in a single scalar value.
- A prediction is considered correct only if the model provides the right label AND cites at least one complete evidence set from the gold-standard annotations.
- This penalizes models that guess the correct label without proper evidence grounding.
- The metric enforces evidence fidelity: a model cannot achieve a high score by memorizing claim-label correlations; it must demonstrate genuine retrieval capability.
The FEVER Score has become a standard for evaluating end-to-end fact verification systems beyond the original dataset.
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.
Frequently Asked Questions
Essential questions about the Fact Extraction and VERification benchmark, its structure, and its role in training automated fact-checking models.
The FEVER (Fact Extraction and VERification) dataset is a large-scale benchmark containing 185,445 claims manually verified against Wikipedia. Each claim is classified as SUPPORTS, REFUTES, or NOT ENOUGH INFO. The dataset was introduced by Thorne et al. in 2018 to train and evaluate models on evidence-based claim verification. Each entry includes a claim, a veracity label, and a set of evidence sentences extracted from Wikipedia pages. Claims were generated by human annotators who rewrote sentences from Wikipedia introductions, then modified them to create refutations. The NOT ENOUGH INFO class represents claims that cannot be verified using Wikipedia alone, requiring models to distinguish between falsity and insufficient evidence—a critical capability for real-world fact-checking systems.
Related Terms
The FEVER dataset is a benchmark, but it sits within a larger ecosystem of computational tasks required to build an end-to-end automated fact-checking pipeline. These related concepts define the upstream and downstream processes.
Claim Detection
The prerequisite step to using FEVER. Claim Detection is the NLP task of identifying check-worthy factual assertions within unstructured text. Before a model can retrieve evidence, it must first segment a document into discrete, verifiable claims.
- Filters out opinions, questions, and subjective statements
- Often uses a check-worthiness classifier to prioritize claims
- Essential for scaling fact-checking to large document volumes
Evidence Retrieval
The first stage of the FEVER task itself. Evidence Retrieval involves searching a corpus (like Wikipedia) to find the most relevant text passages that can support or refute a claim. This is typically performed using dense passage retrieval or BM25 algorithms.
- Converts claims into queries for a document index
- Ranks passages by relevance before passing them to the NLI model
- Poor retrieval is the primary bottleneck in fact verification accuracy
Natural Language Inference
The core reasoning engine behind FEVER. Natural Language Inference (NLI) determines whether a hypothesis (the claim) can be logically inferred from a premise (the evidence). The FEVER dataset uses a three-way classification: Supports, Refutes, or Not Enough Info.
- Distinct from semantic similarity; requires logical reasoning
- Foundation models like RoBERTa fine-tuned on MNLI are common baselines
- Handles the final veracity judgment after evidence is retrieved
Textual Entailment
A directional relationship between text fragments where the truth of a premise logically implies the truth of a hypothesis. Textual Entailment is the formal logic framework underlying NLI and is the mechanism by which FEVER models establish Supports verdicts.
- Example: Premise 'The cat is sleeping on the mat' entails Hypothesis 'A cat is on a mat'
- Contrast with contradiction and neutral relationships
- Used in legal and medical AI for high-stakes reasoning
Veracity Prediction
The final machine learning task that FEVER models are evaluated on. Veracity Prediction classifies a claim as true, false, or mixed based on aggregated evidence and source reliability signals. In FEVER, this is the end-to-end output after joint retrieval and NLI.
- Aggregates multiple evidence sentences into a single judgment
- Real-world systems add source reliability scoring as a weighting factor
- Outputs are used to populate fact-check dashboards and knowledge bases
Justification Production
The explainability layer missing from the original FEVER task but critical for real-world deployment. Justification Production is the NLG step that summarizes the evidence and reasoning behind a veracity decision into human-readable text.
- Generates a concise explanation citing specific evidence sentences
- Transforms opaque model decisions into auditable justifications
- Required for platforms like Google Fact Check Tools and ClaimReview markup

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