Summary

•	Switched GAIA to Parquet-based splits because code-based loaders are deprecated in datasets 4.x.
•	Kept attachments (PDF/PNG/CSV/…) as files on disk.
•	Kept a single file_path (or file_name) column; mixed file types can’t be auto-decoded from one column, so users still open files manually.

Layout

2023/
  validation/
    metadata.parquet
    <attachments...>
  test/
    metadata.parquet
    <attachments...>

Loading

from datasets import load_dataset

ds = load_dataset("gaia-benchmark/GAIA", "2023_level1", split="test")
for ex in ds:
    path = ex.get("file_path") or ex.get("file_name")
    # open path as needed (local or via hf_hub_download)

Notes

•	Existing configs retained: 2023_all, 2023_level1, 2023_level2, 2023_level3.
•	If we ever want auto-decoding, we can add optional typed columns (image/audio/pdf) alongside file_path.
jdubkim changed pull request status to open

Hi there! I'm one of the maintainers of inspect_evals and our implementation of GAIA depends on this dataset. Would it be possible to get this PR merged? Thanks!

Hi @celia-waggoner-aset , I would love to merge this PR but I'm waiting for the owner of this dataset to confirm. @clefourrier is it ok to merge this PR?

GAIA org

Hi! Have not had the time to check it yet - will try to take a look today else Monday

Hi! Thanks again for the PR. I'm facing several issues.

I tried loading your version of the dataset and

  1. it does not seem to download the attachments (I checked locally where I was working and in the cache)
  2. the harcoded paths do not seem to point to anything either
  3. you removed a lot of information from the README

Can you please provide me with the precise command you used to download both the parquet and the files, using datasets? Did you check where the attachments were downloaded?

We'll also likely need to add some info to the readme with said command to make sure people can easily access everything.

@clefourrier Thanks for reviewing this PR!
To be honest, the dataset is not highly compatible with parquet, because GAIA has so many different file formats and HF dataset doesn't support a union of different file types, and some of them are not even supported (.xlsx, .pptx etc). That's why I kept the attachments in the drive and specified the hardcoded file path. If the attachments are not downloaded, that must be my bug (I'll look into this today), but we still have to load the attachments manually. I was going through HF dataset docs for few hours, but this was the cleanest solution I could come with. If someone knows the better solution to this, please let me know!

So, I'll fix the issue where attachments are not downloaded, update README.md with an example code how to load the data.

GAIA org

Thanks! Also pinging @lhoestq , datasets lead, in case he's got an idea for this

You can make it work in two steps:

  1. download the repository using huggingface_hub
  2. load the parquet data containing links to the documents

Here is how you could use it:

import os

from datasets import load_dataset
from huggingface_hub import snapshot_download

data_dir = snapshot_download(repo_id="gaia-benchmark/GAIA", repo_type="dataset")
dataset = load_dataset(data_dir, "2023_level1", split="test")
for example in dataset:
    question = example["question"]
    file_path = os.path.join(data_dir, example["file_path"])

Therefore all we have to do in this PR is making sure the "file_path" column in Parquet contains the path of the file in the repository

GAIA org

So there is no way to have it in one step with datasets ?

GAIA org

(thanks a lot for the answer :) )

Not at the moment, since it doesn't have any logic to handle repos with unknown file types

Hi @clefourrier what is the status of this PR? I would like to use the dataset asap:)

GAIA org

The PR is not ready yet as it changes the README (and notably the gating) as far as I can tell - you can already use the dataset as is by using an older version of the datasets library (before datasets 4.0)

@clefourrier Are you ok with the new method even though this won't download the files automatically? If you're ok with the new way @lhoestq suggested, I'll update the PR today or tomorrow and make sure it's ready.

GAIA org

I think that's the only way to make the dataset compatible with the latest versions of datasets. I'm going to do one last internal check with the other GAIA authors but I think you can go through.

GAIA org

Can confirm other authors are OK for this but let's make the readme ultra clear on the new steps :)

@clefourrier I've updated the README.md to preserve all existing content while adding a new section covering format update details and dataset usage instructions.
Please let me know if you'd like any changes or additions. Thank you for reviewing!

GAIA org

Ok perfect, will review tomorrow!

clefourrier changed pull request status to merged
GAIA org

Merged, thanks again for the great work!

Sign up or log in to comment