The information you provide will be collected, stored, processed and shared in accordance with the Meta Privacy Policy.
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).
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
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:
Log in or Sign Up to review the conditions and access this dataset content.
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.