misc gated 0 0

meta-llama/Llama-3.3-70B-Instruct-evals

published by @meta-llama

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
6.6K
Last 30 days
32
Likes
49
Size
75.5 MB
Created on HF
2024-12-05
Age
1 years ago

Description

Dataset Card for Meta Evaluation Result Details for Llama-3.3-70B-Instruct

This dataset contains the results of the Meta evaluation result details for Llama-3.3-70B-Instruct. The dataset has been created from 12 evaluation tasks. The tasks are: human_eval, mmlu_pro, gpqa_diamond, ifeval__loose, mmlu__0_shot__cot, nih__multi_needle, mgsm, math_hard, bfcl_chat, ifeval__strict, math, mbpp_plus.

Each task detail can be found as a specific subset in each configuration nd each… See the full description on the dataset page: https://huggingface.co/datasets/meta-llama/Llama-3.3-70B-Instruct-evals.

Tags

language:enlicense:llama3.3size_categories:10K<n<100Kformat:parquetmodality:textlibrary:datasetslibrary:pandaslibrary:mlcroissantlibrary:polarsregion:us

README current version from Hugging Face


language: en
license: llama3.3
pretty_name: Meta Evaluation Result Details for Llama-3.3-70B-Instruct
dataset_summary: >+
This dataset contains the results of the Meta evaluation result details for
Llama-3.3-70B-Instruct. The dataset has been created from 12 evaluation
tasks. The tasks are: human_eval, mmlu_pro, gpqa_diamond, ifeval__loose,
mmlu__0_shot__cot, nih__multi_needle, mgsm, math_hard, bfcl_chat,
ifeval__strict, math, mbpp_plus.

Each task detail can be found as a specific subset in each configuration nd 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 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.3-70B-Instruct-evals",
        name="Llama-3.3-70B-Instruct-evals__mbpp_plus__details",
        split="latest"
)

Please check our eval
recipe

that demonstrates how to calculate the our reported benchmark numbers using
the
lm-evaluation-harness
library on selected tasks.

Here are the detailed explanation for each column of 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 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: The answer we’ve parsed from the model output or
calculated using negative log likelihoods.

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
consider 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 truncate

  return_logprobs - Generation parameter - Whether to return log probabilities when generating output.

configs:

  • config_name: Llama-3.3-70B-Instruct-evals__bfcl_chat__details
    data_files:
    • split: latest
      path:

        Llama-3.3-70B-Instruct-evals/Details_bfcl_chat_2024-12-05T16-44-53.191777.parquet.gzip

  • config_name: Llama-3.3-70B-Instruct-evals__gpqa_diamond__details
    data_files:
    • split: latest
      path:

        Llama-3.3-70B-Instruct-evals/Details_gpqa_diamond_2024-12-05T16-44-45.256031.parquet.gzip

  • config_name: Llama-3.3-70B-Instruct-evals__human_eval__details
    data_files:
    • split: latest
      path:

        Llama-3.3-70B-Instruct-evals/Details_human_eval_2024-12-05T16-44-41.991636.parquet.gzip

  • config_name: Llama-3.3-70B-Instruct-evals__ifeval__loose__details
    data_files:
    • split: latest
      path:

        Llama-3.3-70B-Instruct-evals/Details_ifeval__loose_2024-12-05T16-44-45.630953.parquet.gzip

  • config_name: Llama-3.3-70B-Instruct-evals__ifeval__strict__details
    data_files:
    • split: latest
      path:

        Llama-3.3-70B-Instruct-evals/Details_ifeval__strict_2024-12-05T16-44-53.785671.parquet.gzip

  • config_name: Llama-3.3-70B-Instruct-evals__math__details
    data_files:
    • split: latest
      path:

        Llama-3.3-70B-Instruct-evals/Details_math_2024-12-05T16-44-54.263573.parquet.gzip

  • config_name: Llama-3.3-70B-Instruct-evals__math_hard__details
    data_files:
    • split: latest
      path:

        Llama-3.3-70B-Instruct-evals/Details_math_hard_2024-12-05T16-44-52.695530.parquet.gzip

  • config_name: Llama-3.3-70B-Instruct-evals__mbpp_plus__details
    data_files:
    • split: latest
      path:

        Llama-3.3-70B-Instruct-evals/Details_mbpp_plus_2024-12-05T16-44-55.009331.parquet.gzip

  • config_name: Llama-3.3-70B-Instruct-evals__metrics
    data_files:
    • split: latest
      path:

        Llama-3.3-70B-Instruct-evals/Details_metrics_details_2024-12-05T16-44-55.360252.parquet.gzip

  • config_name: Llama-3.3-70B-Instruct-evals__mgsm__details
    data_files:
    • split: latest
      path:

        Llama-3.3-70B-Instruct-evals/Details_mgsm_2024-12-05T16-44-52.199436.parquet.gzip

  • config_name: Llama-3.3-70B-Instruct-evals__mmlu__0_shot__cot__details
    data_files:
    • split: latest
      path:

        Llama-3.3-70B-Instruct-evals/Details_mmlu__0_shot__cot_2024-12-05T16-44-46.184283.parquet.gzip

  • config_name: Llama-3.3-70B-Instruct-evals__mmlu_pro__details
    data_files:
    • split: latest
      path:

        Llama-3.3-70B-Instruct-evals/Details_mmlu_pro_2024-12-05T16-44-42.594223.parquet.gzip

  • config_name: Llama-3.3-70B-Instruct-evals__nih__multi_needle__details
    data_files:
    • split: latest
      path:

        Llama-3.3-70B-Instruct-evals/Details_nih__multi_needle_2024-12-05T16-44-48.274780.parquet.gzip


Dataset Card for Meta Evaluation Result Details for Llama-3.3-70B-Instruct

This dataset contains the results of the Meta evaluation result details for Llama-3.3-70B-Instruct. The dataset has been created from 12 evaluation tasks. The tasks are: human_eval, mmlu_pro, gpqa_diamond, ifeval__loose, mmlu__0_shot__cot, nih__multi_needle, mgsm, math_hard, bfcl_chat, ifeval__strict, math, mbpp_plus.

Each task detail can be found as a specific subset in each configuration nd 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 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.3-70B-Instruct-evals",
        name="Llama-3.3-70B-Instruct-evals__mbpp_plus__details",
        split="latest"
)

Please check our eval recipe that demonstrates how to calculate the our reported benchmark numbers using the lm-evaluation-harness library on selected tasks.

Here are the detailed explanation for each column of 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 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: The answer we’ve parsed from the model output or calculated using negative log likelihoods.

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 consider 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 truncate

return_logprobs - Generation parameter - Whether to return log probabilities when generating output.

README history 6 revisions

Every night we snapshot the README of every dataset in the catalog. When the SHA changes we archive the new version and diff it against the last. This is the evolving thought record of the alignment-data field: what the author decided to say about the corpus, and how that framing shifted over time.

  1. 2024-12-06Update license (#1)cf3641313.1 KB
    Loading...
  2. 2024-12-06Update README.mdb47fc5813.2 KB
    Loading...
  3. 2024-12-06Update README.mdd61455113.2 KB
    Loading...
  4. 2024-12-06Upload README.md with huggingface_hubc4033b617.1 KB
    Loading...
  5. 2024-12-06Adding samples results to Llama-3.3-70B-Instruct-evals52753dc0 B
    Loading...
  6. 2024-12-06initial commitcedc1860 B
    Loading...

Used by abliterated models none yet

No abliterated models in our catalog have declared this dataset in their YAML metadata yet. This can mean the dataset is used but not declared, is used outside abliteration workflows, or is new. The link will populate automatically as models are indexed.

Community discussions 4 threads · 2 open · 5 comments

Threads posted by the community on Hugging Face: bug reports, questions about usage, pull requests on the README, license clarifications. Click any thread to expand and read the full conversation inline. Newest first.

  1. 2025-05-03PRUpdate README.mdclosed2 💬#4
    Loading...
  2. 2024-12-17PRUpdate README.mdopen1 💬#3
    Loading...
  3. 2024-12-07[bot] Conversion to Parquetopen1 💬#2
    Loading...
  4. 2024-12-06PRUpdate licensemerged1 💬#1
    Loading...

Related datasets same stage · misc

Read further

Metadata

License
llama3.3

Repository

Download the dataset

Gated dataset. You need to accept the author's terms on Hugging Face before downloading. Visit the repository, click Agree and access repository, then log in locally with huggingface-cli login and use one of the snippets below.

Copy any of these snippets into your notebook or terminal. All three fetch directly from Hugging Face using your own credentials.

Recommended: datasets library (Python)
from datasets import load_dataset
ds = load_dataset("meta-llama/Llama-3.3-70B-Instruct-evals")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="meta-llama/Llama-3.3-70B-Instruct-evals", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/meta-llama/Llama-3.3-70B-Instruct-evals
Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.

Open in Abliteration