extract 0 0 0

giskardai/phare

published by @giskardai

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
7.5K
Last 30 days
183
Likes
14
Size
22.8 MB
Created on HF
2025-03-25
Age
1 years ago

Description

Phare Benchmark

Phare is a multilingual benchmark that measures LLM Safety across multiple categories of vulnerabilities, including hallucination, biases & stereotypes, harmful content, and jailbreaks.

Dataset Details

Dataset Description

This dataset contains the public set of samples of Phare Benchmark. These samples are split into multiple modules to assess LLM safety across various directions.

Each module is responsible for detecting… See the full description on the dataset page: https://huggingface.co/datasets/giskardai/phare.

Tags

task_categories:text-generationlanguage:frlanguage:enlanguage:eslicense:cc-by-4.0size_categories:1K<n<10Kformat:parquetmodality:textlibrary:datasetslibrary:dasklibrary:mlcroissantlibrary:polarsarxiv:2505.11365region:us

README current version from Hugging Face


language:

  • fr
  • en
  • es
    license: cc-by-4.0
    size_categories:
  • 1K<n<10K
    task_categories:
  • text-generation
    pretty_name: Phare
    configs:
  • config_name: hallucination_tools_basic
    data_files:
    • split: public
      path: hallucination/tools/basic.parquet
  • config_name: hallucination_tools_knowledge
    data_files:
    • split: public
      path: hallucination/tools/knowledge.parquet
  • config_name: hallucination_debunking
    data_files:
    • split: public
      path: hallucination/debunking/*.parquet
  • config_name: hallucination_factuality
    data_files:
    • split: public
      path: hallucination/factuality/*.parquet
  • config_name: hallucination_satirical
    data_files:
    • split: public
      path: hallucination/satirical/*.parquet
  • config_name: harmful_vulnerable_misguidance
    data_files:
    • split: public
      path: harmful/vulnerable_misguidance/*.parquet
  • config_name: biases
    data_files:
    • split: public
      path: biases/story_generation/*.parquet
  • config_name: jailbreak_encoding
    data_files:
    • split: public
      path: jailbreak/jailbreak/encoding.parquet
  • config_name: jailbreak_framing
    data_files:
    • split: public
      path: jailbreak/jailbreak/framing.parquet
  • config_name: jailbreak_injection
    data_files:
    • split: public
      path: jailbreak/jailbreak/injection.parquet

Phare Logo

Phare Benchmark

Phare is a multilingual benchmark that measures LLM Safety across multiple categories of vulnerabilities, including hallucination, biases & stereotypes, harmful content, and jailbreaks.

Dataset Details

Dataset Description

This dataset contains the public set of samples of Phare Benchmark. These samples are split into multiple modules to assess LLM safety across various directions.
Each module is responsible for detecting vulnerabilities in the LLM response:

  • Hallucination: evaluates the factuality and the level of misinformation spread by the models in a question-answer setting. Questions are designed from existing content, including known misinformation or scientifically refuted theories.

  • Biases & stereotypes: assesses the presence of biases in the LLM generations for creative tasks.

  • Harmful content: measures the dangerous behavior endorsement and misguidance rate of LLM with vulnerable people.

  • Jailbreak: measures the robustness of the LLMs against various types of jailbreak attacks (e.g, encoding, role-play, known injection, etc.).

Each module is split into several submodules. The submodules are different approaches to eliciting problematic behavior from the models. For instance, the hallucination modules has several submodules:

  • Debunking: questions about scientifically refuted facts or theories with various levels of bias
  • Satirical: questions derived from misinformation and satirical sources
  • Factuality: questions about generic facts
  • Tools: questions that can be answered with the use of a tool available for the model, to measure hallucination in tool parameters and correct tool usage.

Extra information

  • Author: Giskard AI
  • Language(s): English, French, Spanish
  • License: CC BY 4.0, except for the Jailbreak module, which is licensed under AGPL-3.0

Dataset Structure

The dataset is split into a public (available in this repository) and a private sets. Giskard reserves the private set to run the Phare Benchmark and keep the leaderboard up-to-date.

Each submodule is a set of .jsonl files containing the samples.
Each sample in these files has the following structure:

{
  "id": # unique id of the sample
  "module": # the module the sample belongs to
  "task": # the submodule or task the sample belongs to
  "language": # the language of the sampel
  "generations": # a list of generations/completions that will be performed for the given sample
      [{
        "id": # unique id of the generation
        "type": # the type of completion, currently only support s`chat_completion`
        "messages": # the list of messages to complete
        "params": # a dictionary with optional generation params (temperature, tools, etc.)
  }]
  "metadata": # a dictionary of metadata, with mainly information about the generation process of the sample
  "evaluation": # a dictionary with additional elements required for the automatic evaluation of the response (include context about the question, expected answers, etc.), changes from between submodules.
}

Dataset Creation

Curation Rationale

Most safety evaluation datasets lack comprehensiveness and multicultural support. Our main goal with Phare is to fill this gap and propose a benchmark that detects inappropriate behavior in various situations.
In addition, the dataset was designed in multiple languages from scratch, including the data collection phase to ensure multicultural diversity.

Source Data

Data sources are diverse and change for each module:

  • Hallucinations: news articles, wikipedia articles, satirical articles, forum threads, etc.
  • Harmful content: examples of AI incident from https://incidentdatabase.ai/
  • Biases & Stereotypes: legal documents about discriminatory attributes.
  • Jailbreak: existing dataset of well known attacks, precise attributions are available under jailbreak/LICENSE.md.

The Hallucination module uses the source data more extensively than other modules. The hallucination questions are grounded on existing content, while for other modules, the data source only influences the evaluation process, e.g. legislation about discrimination fixes the attributes that are extracted from the LLM answers.

Data Collection and Processing

Data collection and filtering were done semi-automatically by the Giskard team. The initial steps of data collection and filtering were done automatically with diverse criteria depending on the module.

Following the data collection and filtering step, the samples are generated using diverse strategies. It includes a combination of LLM generation and the application of handcrafted templates. All details about the generation process are available in our technical report.

A manual review was then conducted on the generated samples by native speakers of the corresponding language to make sure the samples were meeting our quality criteria.

Personal and Sensitive Information

The dataset contains samples that can be sensitive or misleading. In particular, the harmful content module contains samples that push for dangerous behavior. Similarly, the hallucination module contains samples made of factually false content.

Bias, Risks, and Limitations

  • Some content was generated with the help of LLMs and can be imperfect.
  • Some data sources used in particular in the hallucination module can be partial.
  • The evaluation process is automatic and is not fully accurate, we measured the evaluation quality manually on each submodule individually to ensure the errors are constrained. Results of this analysis will be reported precisely in the technical paper.
  • The team that manually reviewed the samples and the evaluation results has limited representativity.
  • Some modules and languages have more samples than others and will have more influence on the aggregated scores.
  • Private and public splits representativity differs across modules.

Dataset Card Contact

README history 20 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. 2025-12-11Update README.md7662ff08 KB
    Loading...
  2. 2025-12-10Update README.md53cb8f18 KB
    Loading...
  3. 2025-12-10Update README.mdcf138b98 KB
    Loading...
  4. 2025-12-09Update README.md08057e87.3 KB
    Loading...
  5. 2025-12-09Update README.md88830417.3 KB
    Loading...
  6. 2025-12-09Upload folder using huggingface_hub403c5537 KB
    Loading...
  7. 2025-12-09Upload folder using huggingface_hub2772ab67 KB
    Loading...
  8. 2025-06-06Add link to the paper (#5)01b52557 KB
    Loading...
  9. 2025-05-21Update README.md08cbd9d7 KB
    Loading...
  10. 2025-05-15Upload folder using huggingface_hub756b3af7 KB
    Loading...
  11. 2025-05-06Update README.md36a37cc7 KB
    Loading...
  12. 2025-05-05Update README.md64f17557 KB
    Loading...
  13. 2025-05-05Upload folder using huggingface_hubd84e8137 KB
    Loading...
  14. 2025-05-05Update README.md9bd41d47 KB
    Loading...
  15. 2025-05-05Delete harmful67118b67 KB
    Loading...
  16. 2025-05-05Delete hallucinationf8e18777 KB
    Loading...
  17. 2025-05-05Delete biases557f16c7 KB
    Loading...
  18. 2025-05-05Upload folder using huggingface_hub10da2af7 KB
    Loading...
  19. 2025-05-05Delete harmful76223227 KB
    Loading...
  20. 2025-05-05Delete hallucinationde5c3477 KB
    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 · 1 open · 7 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-22PRAdd link to the papermerged2 💬#5
    Loading...
  2. 2025-05-02PRParquet Uploadmerged1 💬#4
    Loading...
  3. 2025-04-05The technical report link in the readme gives a 404closed3 💬#2
    Loading...
  4. 2025-04-03[bot] Conversion to Parquetopen1 💬#1
    Loading...

Related datasets same stage · extract

Read further

Metadata

License
cc-by-4.0

Repository

Download the dataset

0

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("giskardai/phare")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="giskardai/phare", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/giskardai/phare
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