misc 0 0 0

dreadnode/grt2

published by @dreadnode

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
1.4K
Last 30 days
68
Likes
10
Size
325.9 MB
Created on HF
2024-08-26
Age
2 years ago

Description

AI Village - Generative Red Team 2 Dataset

Data Dictionary

At Defcon 32, the AI Village hosted the 2nd Generative Red Teaming event (GRT2). This dataset contains all the raw data collected during the event.

The dataset is provided in both csv and parquet formats for convenience.

Inference (grt2_inference.csv/grt2_inference.parquet)

Contains all inference requests sent to the OLMo API endpoint during the GRT2 event. All samples contained in runs… See the full description on the dataset page: https://huggingface.co/datasets/dreadnode/grt2.

Tags

license:apache-2.0size_categories:100K<n<1Mformat:parquetmodality:tabularmodality:textlibrary:datasetslibrary:pandaslibrary:mlcroissantlibrary:polarsregion:usnot-for-all-audiences

README current version from Hugging Face


license: apache-2.0
configs:

  • config_name: inference
    data_files: grt2_inference.parquet
  • config_name: runs
    data_files: grt2_runs.parquet
  • config_name: samples
    data_files: grt2_samples.parquet
  • config_name: submissions
    data_files: grt2_submissions.parquet
    tags:
  • not-for-all-audiences

AI Village - Generative Red Team 2 Dataset

Data Dictionary

At Defcon 32, the AI Village hosted the 2nd Generative Red Teaming event (GRT2). This dataset contains all the raw data collected during the event.

The dataset is provided in both csv and parquet formats for convenience.

Inference (grt2_inference.csv/grt2_inference.parquet)

Contains all inference requests sent to the OLMo API endpoint during the GRT2 event. All samples contained in runs and/or submissions are included in this dataset, along with any requests that were not part of a submission.

  • id: Unique identifier for each inference request.
  • timestamp: Timestamp of the request.
  • status_code: API status code response to the request (200/400/404).
  • request_message: Message sent to the OLMo model.
  • response_message: Response from the OLMo model.

Runs (grt2_runs.csv/grt2_runs.parquet)

Contains metadata about runs created by users. Each row represents a unique run that may or may not have been included in a submission.

  • run_id: Unique identifier for the run.
  • user_id: Identifier of the user who created the run.
  • commentary: Additional commentary provided by the user.
  • eval_name: Evaluation type chosen by the user when creating the run. Options: 'privacy', 'harmful-language', 'misinformation', 'malicious-uses', or 'custom'.
  • submission_ids: List of submission identifiers in which the run was included.
  • created_at: Datetime of run creation.
  • primary_scorer: Name of the primary scorer.
  • primary_score: Value of the primary score.
  • secondary_scorer: Type of the secondary scorer (if available).
  • secondary_score: Value of the secondary score (if available).

Submissions (grt2_submissions.csv/grt2_submissions.parquet)

Contains all submissions created by users from one or more runs, including information on monetary awards.

  • submission_id: Unique identifier for each submission.
  • user_id: Identifier of the user who created the submission.
  • eval_name: Evaluation type, similar to eval_name in the runs dataset.
  • commentary: Additional commentary provided by the user.
  • run_ids: One or more run identifiers used in the submission.
  • evidence: Any evidence files included by the user.
  • created_at: Datetime of submission creation.
  • created_type: Either 'API' or 'UI', indicating whether the submission was created using the Crucible user interface (UI) or uploaded via the Crucible web API endpoint.
  • status: Either 'draft' if not submitted to Bugcrowd, or 'new' if submitted.
  • bugcrowd_id: Unique identifier for the submission in Bugcrowd.
  • monetary_amount: Total USD payout for the submission.

Samples (grt2_samples.csv, grt2_samples.parquet)

Contains all request/response pairs linked to a given run with scoring output.

  • run_id: Unique identifier of the run that the sample is linked to.
  • sample_id: Sample identifier within the run (may not be unique if epoch > 1).
  • epoch: If > 1, indicates the same input was run multiple times.
  • input: Raw input text.
  • response: Response text from the model.
  • Score columns (contain a value if the given scoring metric was enabled, otherwise null):
    • crucible/presidio.value: Presidio score value (if available).
    • crucible/wildguard.value: WildGuard score value (if available).
    • crucible/perspective.value: Perspective score value (if available).
    • crucible/zero_shot.value: Score from a zero-shot classifier (if available).
    • model_graded_qa.value: Score from a model-graded QA.
    • crucible/wildguard.metadata.harmful_request: Boolean value indicating if identified as a harmful request by WildGuard.
    • crucible/wildguard.metadata.refusal_response: Boolean value indicating if identified as a refusal response by WildGuard.
    • crucible/wildguard.metadata.harmful_response: Boolean value indicating if response identified as harmful by WildGuard.

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-09-20Add NFAA tag (#2)d8bd7644.2 KB
    Loading...
  2. 2024-08-26Update README.mdb38168f4.1 KB
    Loading...
  3. 2024-08-26Update README.mddfc5b8d282 B
    Loading...
  4. 2024-08-26Update README.mdd046704286 B
    Loading...
  5. 2024-08-26Upload 8 filescfbe7ca31 B
    Loading...
  6. 2024-08-26initial commit1f745ee31 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 2 threads · 1 open · 3 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. 2024-09-20PRAdd NFAA tagmerged2 💬#2
    Loading...
  2. 2024-08-27[bot] Conversion to Parquetopen1 💬#1
    Loading...

Related datasets same stage · misc

Read further

Metadata

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