Datasets:
metadata
language: en
license: llama3.1
pretty_name: Llama-3.1-405B Evaluation Result Details
dataset_summary: "This dataset contains the Meta evaluation result details for **Llama-3.1-405B**. The dataset has been created from 12 evaluation tasks. These tasks are triviaqa__wiki, mmlu_pro, commonsenseqa, winogrande, mmlu, boolq, squad, quac, drop, bbh, arc_challenge, agieval_english. \n\nEach task detail can be found as a specific subset in each configuration and each subset is named using the task name plus the timestamp of the upload time and ends with \"__details\".\n\nFor more information about the eval tasks, please refer to this [eval details](https://github.com/meta-llama/llama-models/blob/main/models/llama3_1/eval_details.md) page.\n\nYou can use the Viewer feature to view the dataset in the web browser easily. For most tasks, we provide an \"**is_correct**\" column, so you can quickly get our accuracy result of the task by viewing the percentage of \"is_correct=True\". For tasks that have both binary (eg. exact_match) and a continuous metrics (eg. f1), we will only consider the binary metric for adding the is_correct column. This might differ from the reported metric in the Llama 3.1 model card.\n\nAdditionally, there is a model metrics subset that contains all the reported metrics, like f1, macro_avg/acc, for all the tasks and subtasks. Please use this subset to find reported metrics in the model card.\n\nLastly, you can also use Huggingface Dataset APIs to load the dataset. For example, to load a eval task detail, you can use the following code:\n```python\nfrom datasets import load_dataset\ndata = load_dataset(\n\t\"meta-llama/Llama-3.1-405B-evals\",\n\tname=\"Llama-3.1-405B-evals__agieval_english__details\",\n\tsplit=\"latest\"\n\t)\n```\n\nHere are the explanations for each column in the task eval details:\n\n**task_type**: Whether the eval task was run as a ‘Generative’ or ‘Choice’ task. Generative task returns the model output, whereas for choice tasks we return the negative log likelihoods of the completion. (The choice task approach is typically used for multiple choice tasks for non-instruct models)\n\n**task_name**: Meta's internal eval task name\n\n**subtask_name**: Meta internal subtask name in cases where the benchmark has subcategories (Ex. MMLU with domains)\n\n**input_question**: The question from the input dataset when available. In cases when that data is overwritten as a part of the evaluation pipeline or it is a complex concatenation of input dataset fields, this will be the serialized prompt object as a string.\n\n**input_choice_list**: In the case of multiple choice questions, this contains a map of the choice name to the text.\n\n**input_final_prompt**: The final input text that is provided to the model for inference. For choice tasks, this will be an array of prompts provided to the model, where we calculate the likelihoods of the different completions in order to get the final answer provided by the model.\n\n**input_correct_responses**: An array of correct responses to the input question.\n\n**output_prediction_text**: The model output for a Generative task \n\n**output_parsed_answer**: Typically answer we’ve parsed from the model output or calculated using negative log likelihoods. Sometimes this is a interpolation of answers parsed from the model output and fields from the benchmark example\n\n**output_choice_completions**: For choice tasks, the list of completions we’ve provided to the model to calculate negative log likelihoods\n\n**output_choice_negative_log_likelihoods**: For choice tasks, these are the corresponding negative log likelihoods normalized by different sequence lengths (text, token, raw) for the above completions.\n\n**output_metrics**: Metrics calculated at the example level. Common metrics include:\n\n acc - accuracy\n\n em - exact_match\n\n f1 - F1 score\n\n pass@1 - For coding benchmarks, whether the output code passes tests\n\n**is_correct**: Whether the parsed answer matches the target responses and is considered correct. (Only applicable for benchmarks which have such a boolean metric)\n\n**input_question_hash**: The SHA256 hash of the question text encoded as UTF-8\n\n**input_final_prompts_hash**: An array of SHA256 hash of the input prompt text encoded as UTF-8\n\n**benchmark_label**: The commonly used benchmark name\n\n**eval_config**: Additional metadata related to the configurations we used to run this evaluation:\n\n num_generations - Generation parameter - how many outputs to generate\n\n num_shots - How many few shot examples to include in the prompt.\n\n max_gen_len - generation parameter (how many tokens to generate)\n\n prompt_fn - The prompt function with jinja template when available\n\n max_prompt_len - Generation parameter. Maximum number tokens for the prompt. If the input_final_prompt is longer than this configuration, we will truncat\n\n return_logprobs - Generation parameter - Whether to return log probabilities when generating output.\n\n\n\n"
configs:
- config_name: Llama-3.1-405B-evals__agieval_english__details
data_files:
- split: latest
path:
- >-
Llama-3.1-405B-evals/Details_agieval_english_2024-07-22T14-59-46.941764.parquet.gzip
- config_name: Llama-3.1-405B-evals__arc_challenge__details
data_files:
- split: latest
path:
- >-
Llama-3.1-405B-evals/Details_arc_challenge_2024-07-22T14-59-46.063233.parquet.gzip
- config_name: Llama-3.1-405B-evals__bbh__details
data_files:
- split: latest
path:
- >-
Llama-3.1-405B-evals/Details_bbh_2024-07-22T14-59-45.318516.parquet.gzip
- config_name: Llama-3.1-405B-evals__boolq__details
data_files:
- split: latest
path:
- >-
Llama-3.1-405B-evals/Details_boolq_2024-07-22T14-59-40.219593.parquet.gzip
- config_name: Llama-3.1-405B-evals__commonsenseqa__details
data_files:
- split: latest
path:
- >-
Llama-3.1-405B-evals/Details_commonsenseqa_2024-07-22T14-59-37.087919.parquet.gzip
- config_name: Llama-3.1-405B-evals__drop__details
data_files:
- split: latest
path:
- >-
Llama-3.1-405B-evals/Details_drop_2024-07-22T14-59-43.311295.parquet.gzip
- config_name: Llama-3.1-405B-evals__metrics
data_files:
- split: latest
path:
- >-
Llama-3.1-405B-evals/Details_metrics_details_2024-07-22T14-59-47.610318.parquet.gzip
- config_name: Llama-3.1-405B-evals__mmlu__details
data_files:
- split: latest
path:
- >-
Llama-3.1-405B-evals/Details_mmlu_2024-07-22T14-59-38.070997.parquet.gzip
- config_name: Llama-3.1-405B-evals__mmlu_pro__details
data_files:
- split: latest
path:
- >-
Llama-3.1-405B-evals/Details_mmlu_pro_2024-07-22T14-59-35.297808.parquet.gzip
- config_name: Llama-3.1-405B-evals__quac__details
data_files:
- split: latest
path:
- >-
Llama-3.1-405B-evals/Details_quac_2024-07-22T14-59-41.804626.parquet.gzip
- config_name: Llama-3.1-405B-evals__squad__details
data_files:
- split: latest
path:
- >-
Llama-3.1-405B-evals/Details_squad_2024-07-22T14-59-40.780471.parquet.gzip
- config_name: Llama-3.1-405B-evals__triviaqa__wiki__details
data_files:
- split: latest
path:
- >-
Llama-3.1-405B-evals/Details_triviaqa__wiki_2024-07-22T14-59-34.605024.parquet.gzip
- config_name: Llama-3.1-405B-evals__winogrande__details
data_files:
- split: latest
path:
- >-
Llama-3.1-405B-evals/Details_winogrande_2024-07-22T14-59-37.488762.parquet.gzip
extra_gated_prompt: >-
### LLAMA 3.1 COMMUNITY LICENSE AGREEMENT
Llama 3.1 Version Release Date: July 23, 2024
"Agreement" means the terms and conditions for use, reproduction, distribution
and modification of the Llama Materials set forth herein.
"Documentation" means the specifications, manuals and documentation
accompanying Llama 3.1 distributed by Meta at
https://llama.meta.com/doc/overview.
"Licensee" or "you" means you, or your employer or any other person or entity
(if you are entering into this Agreement on such person or entity’s behalf),
of the age required under applicable laws, rules or regulations to provide
legal consent and that has legal authority to bind your employer or such other
person or entity if you are entering in this Agreement on their behalf.
"Llama 3.1" means the foundational large language models and software and
algorithms, including machine-learning model code, trained model weights,
inference-enabling code, training-enabling code, fine-tuning enabling code and
other elements of the foregoing distributed by Meta at
https://llama.meta.com/llama-downloads.
"Llama Materials" means, collectively, Meta’s proprietary Llama 3.1 and
Documentation (and any portion thereof) made available under this Agreement.
"Meta" or "we" means Meta Platforms Ireland Limited (if you are located in or,
if you are an entity, your principal place of business is in the EEA or
Switzerland) and Meta Platforms, Inc. (if you are located outside of the EEA
or Switzerland).
1. License Rights and Redistribution.
a. Grant of Rights. You are granted a non-exclusive, worldwide,
non-transferable and royalty-free limited license under Meta’s intellectual
property or other rights owned by Meta embodied in the Llama Materials to use,
reproduce, distribute, copy, create derivative works of, and make
modifications to the Llama Materials.
b. Redistribution and Use.
i. If you distribute or make available the Llama Materials (or any derivative
works thereof), or a product or service (including another AI model) that
contains any of them, you shall (A) provide a copy of this Agreement with any
such Llama Materials; and (B) prominently display “Built with Llama” on a
related website, user interface, blogpost, about page, or product
documentation. If you use the Llama Materials or any outputs or results of the
Llama Materials to create, train, fine tune, or otherwise improve an AI model,
which is distributed or made available, you shall also include “Llama” at the
beginning of any such AI model name.
ii. If you receive Llama Materials, or any derivative works thereof, from a
Licensee as part of an integrated end user product, then Section 2 of this
Agreement will not apply to you.
iii. You must retain in all copies of the Llama Materials that you distribute
the following attribution notice within a “Notice” text file distributed as a
part of such copies: “Llama 3.1 is licensed under the Llama 3.1 Community
License, Copyright © Meta Platforms, Inc. All Rights Reserved.”
iv. Your use of the Llama Materials must comply with applicable laws and
regulations (including trade compliance laws and regulations) and adhere to
the Acceptable Use Policy for the Llama Materials (available at
https://llama.meta.com/llama3_1/use-policy), which is hereby incorporated by
reference into this Agreement.
2. Additional Commercial Terms. If, on the Llama 3.1 version release date, the
monthly active users of the products or services made available by or for
Licensee, or Licensee’s affiliates, is greater than 700 million monthly active
users in the preceding calendar month, you must request a license from Meta,
which Meta may grant to you in its sole discretion, and you are not authorized
to exercise any of the rights under this Agreement unless or until Meta
otherwise expressly grants you such rights.
3. Disclaimer of Warranty. UNLESS REQUIRED BY APPLICABLE LAW, THE LLAMA
MATERIALS AND ANY OUTPUT AND RESULTS THEREFROM ARE PROVIDED ON AN “AS IS”
BASIS, WITHOUT WARRANTIES OF ANY KIND, AND META DISCLAIMS ALL WARRANTIES OF
ANY KIND, BOTH EXPRESS AND IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY
WARRANTIES OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A
PARTICULAR PURPOSE. YOU ARE SOLELY RESPONSIBLE FOR DETERMINING THE
APPROPRIATENESS OF USING OR REDISTRIBUTING THE LLAMA MATERIALS AND ASSUME ANY
RISKS ASSOCIATED WITH YOUR USE OF THE LLAMA MATERIALS AND ANY OUTPUT AND
RESULTS.
4. Limitation of Liability. IN NO EVENT WILL META OR ITS AFFILIATES BE LIABLE
UNDER ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, TORT, NEGLIGENCE, PRODUCTS
LIABILITY, OR OTHERWISE, ARISING OUT OF THIS AGREEMENT, FOR ANY LOST PROFITS
OR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL, EXEMPLARY OR PUNITIVE
DAMAGES, EVEN IF META OR ITS AFFILIATES HAVE BEEN ADVISED OF THE POSSIBILITY
OF ANY OF THE FOREGOING.
5. Intellectual Property.
a. No trademark licenses are granted under this Agreement, and in connection
with the Llama Materials, neither Meta nor Licensee may use any name or mark
owned by or associated with the other or any of its affiliates, except as
required for reasonable and customary use in describing and redistributing the
Llama Materials or as set forth in this Section 5(a). Meta hereby grants you a
license to use “Llama” (the “Mark”) solely as required to comply with the last
sentence of Section 1.b.i. You will comply with Meta’s brand guidelines
(currently accessible at
https://about.meta.com/brand/resources/meta/company-brand/ ). All goodwill
arising out of your use of the Mark will inure to the benefit of Meta.
b. Subject to Meta’s ownership of Llama Materials and derivatives made by or
for Meta, with respect to any derivative works and modifications of the Llama
Materials that are made by you, as between you and Meta, you are and will be
the owner of such derivative works and modifications.
c. If you institute litigation or other proceedings against Meta or any entity
(including a cross-claim or counterclaim in a lawsuit) alleging that the Llama
Materials or Llama 3.1 outputs or results, or any portion of any of the
foregoing, constitutes infringement of intellectual property or other rights
owned or licensable by you, then any licenses granted to you under this
Agreement shall terminate as of the date such litigation or claim is filed or
instituted. You will indemnify and hold harmless Meta from and against any
claim by any third party arising out of or related to your use or distribution
of the Llama Materials.
6. Term and Termination. The term of this Agreement will commence upon your
acceptance of this Agreement or access to the Llama Materials and will
continue in full force and effect until terminated in accordance with the
terms and conditions herein. Meta may terminate this Agreement if you are in
breach of any term or condition of this Agreement. Upon termination of this
Agreement, you shall delete and cease use of the Llama Materials. Sections 3,
4 and 7 shall survive the termination of this Agreement.
7. Governing Law and Jurisdiction. This Agreement will be governed and
construed under the laws of the State of California without regard to choice
of law principles, and the UN Convention on Contracts for the International
Sale of Goods does not apply to this Agreement. The courts of California shall
have exclusive jurisdiction of any dispute arising out of this Agreement.
### Llama 3.1 Acceptable Use Policy
Meta is committed to promoting safe and fair use of its tools and features,
including Llama 3.1. If you access or use Llama 3.1, you agree to this
Acceptable Use Policy (“Policy”). The most recent copy of this policy can be
found at
[https://llama.meta.com/llama3_1/use-policy](https://llama.meta.com/llama3_1/use-policy)
#### Prohibited Uses
We want everyone to use Llama 3.1 safely and responsibly. You agree you will
not use, or allow others to use, Llama 3.1 to:
1. Violate the law or others’ rights, including to:
1. Engage in, promote, generate, contribute to, encourage, plan, incite, or further illegal or unlawful activity or content, such as:
1. Violence or terrorism
2. Exploitation or harm to children, including the solicitation, creation, acquisition, or dissemination of child exploitative content or failure to report Child Sexual Abuse Material
3. Human trafficking, exploitation, and sexual violence
4. The illegal distribution of information or materials to minors, including obscene materials, or failure to employ legally required age-gating in connection with such information or materials.
5. Sexual solicitation
6. Any other criminal activity
3. Engage in, promote, incite, or facilitate the harassment, abuse, threatening, or bullying of individuals or groups of individuals
4. Engage in, promote, incite, or facilitate discrimination or other unlawful or harmful conduct in the provision of employment, employment benefits, credit, housing, other economic benefits, or other essential goods and services
5. Engage in the unauthorized or unlicensed practice of any profession including, but not limited to, financial, legal, medical/health, or related professional practices
6. Collect, process, disclose, generate, or infer health, demographic, or other sensitive personal or private information about individuals without rights and consents required by applicable laws
7. Engage in or facilitate any action or generate any content that infringes, misappropriates, or otherwise violates any third-party rights, including the outputs or results of any products or services using the Llama Materials
8. Create, generate, or facilitate the creation of malicious code, malware, computer viruses or do anything else that could disable, overburden, interfere with or impair the proper working, integrity, operation or appearance of a website or computer system
2. Engage in, promote, incite, facilitate, or assist in the planning or
development of activities that present a risk of death or bodily harm to
individuals, including use of Llama 3.1 related to the following:
1. Military, warfare, nuclear industries or applications, espionage, use for materials or activities that are subject to the International Traffic Arms Regulations (ITAR) maintained by the United States Department of State
2. Guns and illegal weapons (including weapon development)
3. Illegal drugs and regulated/controlled substances
4. Operation of critical infrastructure, transportation technologies, or heavy machinery
5. Self-harm or harm to others, including suicide, cutting, and eating disorders
6. Any content intended to incite or promote violence, abuse, or any infliction of bodily harm to an individual
3. Intentionally deceive or mislead others, including use of Llama 3.1 related
to the following:
1. Generating, promoting, or furthering fraud or the creation or promotion of disinformation
2. Generating, promoting, or furthering defamatory content, including the creation of defamatory statements, images, or other content
3. Generating, promoting, or further distributing spam
4. Impersonating another individual without consent, authorization, or legal right
5. Representing that the use of Llama 3.1 or outputs are human-generated
6. Generating or facilitating false online engagement, including fake reviews and other means of fake online engagement
4. Fail to appropriately disclose to end users any known dangers of your AI
system
Please report any violation of this Policy, software “bug,” or other problems
that could lead to a violation of this Policy through one of the following
means:
* Reporting issues with the model: [https://github.com/meta-llama/llama-models/issues](https://github.com/meta-llama/llama-models/issues)
* Reporting risky content generated by the model:
developers.facebook.com/llama_output_feedback
* Reporting bugs and security concerns: facebook.com/whitehat/info
* Reporting violations of the Acceptable Use Policy or unlicensed uses of Meta Llama 3: LlamaUseReport@meta.com
extra_gated_fields:
First Name: text
Last Name: text
Date of birth: date_picker
Country: country
Affiliation: text
Job title:
type: select
options:
- Student
- Research Graduate
- AI researcher
- AI developer/engineer
- Reporter
- Other
geo: ip_location
By clicking Submit below I accept the terms of the license and acknowledge that the information I provide will be collected stored processed and shared in accordance with the Meta Privacy Policy: checkbox
extra_gated_description: >-
The information you provide will be collected, stored, processed and shared in
accordance with the [Meta Privacy
Policy](https://www.facebook.com/privacy/policy/).
extra_gated_button_content: Submit
Dataset Card for Llama-3.1-405B Evaluation Result Details
This dataset contains the Meta evaluation result details for Llama-3.1-405B. The dataset has been created from 12 evaluation tasks. These tasks are triviaqa__wiki, mmlu_pro, commonsenseqa, winogrande, mmlu, boolq, squad, quac, drop, bbh, arc_challenge, agieval_english.
Each task detail can be found as a specific subset in each configuration and each subset is named using the task name plus the timestamp of the upload time and ends with "__details".
For more information about the eval tasks, please refer to this eval details page.
You can use the Viewer feature to view the dataset in the web browser easily. For most tasks, we provide an "is_correct" column, so you can quickly get our accuracy result of the task by viewing the percentage of "is_correct=True". For tasks that have both binary (eg. exact_match) and a continuous metrics (eg. f1), we will only consider the binary metric for adding the is_correct column. This might differ from the reported metric in the Llama 3.1 model card.
Additionally, there is a model metrics subset that contains all the reported metrics, like f1, macro_avg/acc, for all the tasks and subtasks. Please use this subset to find reported metrics in the model card.
Lastly, you can also use Huggingface Dataset APIs to load the dataset. For example, to load a eval task detail, you can use the following code:
from datasets import load_dataset
data = load_dataset(
"meta-llama/Llama-3.1-405B-evals",
name="Llama-3.1-405B-evals__agieval_english__details",
split="latest"
)
Please check our eval recipe that demonstrates how to calculate the Llama 3.1 reported benchmark numbers using the lm-evaluation-harness library and the datasets in 3.1 evals collections on selected tasks.
Here are the explanations for each column in the task eval details:
task_type: Whether the eval task was run as a ‘Generative’ or ‘Choice’ task. Generative task returns the model output, whereas for choice tasks we return the negative log likelihoods of the completion. (The choice task approach is typically used for multiple choice tasks for non-instruct models)
task_name: Meta's internal eval task name
subtask_name: Meta internal subtask name in cases where the benchmark has subcategories (Ex. MMLU with domains)
input_question: The question from the input dataset when available. In cases when that data is overwritten as a part of the evaluation pipeline or it is a complex concatenation of input dataset fields, this will be the serialized prompt object as a string.
input_choice_list: In the case of multiple choice questions, this contains a map of the choice name to the text.
input_final_prompt: The final input text that is provided to the model for inference. For choice tasks, this will be an array of prompts provided to the model, where we calculate the likelihoods of the different completions in order to get the final answer provided by the model.
input_correct_responses: An array of correct responses to the input question.
output_prediction_text: The model output for a Generative task
output_parsed_answer: Typically answer we’ve parsed from the model output or calculated using negative log likelihoods. Sometimes this is a interpolation of answers parsed from the model output and fields from the benchmark example
output_choice_completions: For choice tasks, the list of completions we’ve provided to the model to calculate negative log likelihoods
output_choice_negative_log_likelihoods: For choice tasks, these are the corresponding negative log likelihoods normalized by different sequence lengths (text, token, raw) for the above completions.
output_metrics: Metrics calculated at the example level. Common metrics include:
acc - accuracy
em - exact_match
f1 - F1 score
pass@1 - For coding benchmarks, whether the output code passes tests
is_correct: Whether the parsed answer matches the target responses and is considered correct. (Only applicable for benchmarks which have such a boolean metric)
input_question_hash: The SHA256 hash of the question text encoded as UTF-8
input_final_prompts_hash: An array of SHA256 hash of the input prompt text encoded as UTF-8
benchmark_label: The commonly used benchmark name
eval_config: Additional metadata related to the configurations we used to run this evaluation:
num_generations - Generation parameter - how many outputs to generate
num_shots - How many few shot examples to include in the prompt.
max_gen_len - generation parameter (how many tokens to generate)
prompt_fn - The prompt function with jinja template when available
max_prompt_len - Generation parameter. Maximum number tokens for the prompt. If the input_final_prompt is longer than this configuration, we will truncat
return_logprobs - Generation parameter - Whether to return log probabilities when generating output.