Datasets:

Languages:
Dutch
ArXiv:
License:
Dataset Preview
Full Screen
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
The dataset generation failed because of a cast error
Error code:   DatasetGenerationCastError
Exception:    DatasetGenerationCastError
Message:      An error occurred while generating the dataset

All the data files must have the same columns, but at some point there are 1 new columns ({'title'})

This happened while the json dataset builder was generating data using

hf://datasets/clips/beir-nl-webis-touche2020/corpus.jsonl (at revision f96b5f6ed29931e9f817bba0f5a37d8b25abd63f)

Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)
Traceback:    Traceback (most recent call last):
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1870, in _prepare_split_single
                  writer.write_table(table)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/arrow_writer.py", line 622, in write_table
                  pa_table = table_cast(pa_table, self._schema)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/table.py", line 2292, in table_cast
                  return cast_table_to_schema(table, schema)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/table.py", line 2240, in cast_table_to_schema
                  raise CastError(
              datasets.table.CastError: Couldn't cast
              _id: string
              title: string
              text: string
              to
              {'_id': Value(dtype='string', id=None), 'text': Value(dtype='string', id=None)}
              because column names don't match
              
              During handling of the above exception, another exception occurred:
              
              Traceback (most recent call last):
                File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1417, in compute_config_parquet_and_info_response
                  parquet_operations = convert_to_parquet(builder)
                File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1049, in convert_to_parquet
                  builder.download_and_prepare(
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 924, in download_and_prepare
                  self._download_and_prepare(
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1000, in _download_and_prepare
                  self._prepare_split(split_generator, **prepare_split_kwargs)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1741, in _prepare_split
                  for job_id, done, content in self._prepare_split_single(
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1872, in _prepare_split_single
                  raise DatasetGenerationCastError.from_cast_error(
              datasets.exceptions.DatasetGenerationCastError: An error occurred while generating the dataset
              
              All the data files must have the same columns, but at some point there are 1 new columns ({'title'})
              
              This happened while the json dataset builder was generating data using
              
              hf://datasets/clips/beir-nl-webis-touche2020/corpus.jsonl (at revision f96b5f6ed29931e9f817bba0f5a37d8b25abd63f)
              
              Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)

Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.

_id
string
text
string
1
Moeten leraren een vast contract krijgen?
2
Is dampen met e-sigaretten veilig?
3
Moet insider trading toegestaan zijn?
4
Moet er lichamelijke straf worden toegepast op scholen?
5
Moet de sociale zekerheid worden geprivatiseerd?
6
Is een universitaire opleiding de moeite waard?
7
Moeten veroordeelden die hun straf hebben uitgezeten mogen stemmen?
8
Moet abortus legaal zijn?
9
Moeten leerlingen een schooluniform dragen?
10
Moeten er vaccins verplicht worden voor kinderen?
11
Moeten prestatieverhogende middelen in de sport worden geaccepteerd?
12
Moeten anticonceptiepillen zonder recept verkrijgbaar zijn?
13
Kan alternatieve energie fossiele brandstoffen effectief vervangen?
14
Wordt seksuele geaardheid bij de geboorte bepaald?
15
Moeten dieren gebruikt worden voor wetenschappelijk of commercieel testen?
16
Moeten geneesmiddelen op recept rechtstreeks aan consumenten worden geadverteerd?
17
Moet recreatieve marihuana legaal zijn?
18
Moeten kerken belastingvrij blijven?
19
Moet het homohuwelijk legaal zijn?
20
Is het drinken van melk gezond voor mensen?
21
Is de mensheid hoofdzakelijk verantwoordelijk voor de klimaatverandering?
22
Is een tweestatenoplossing een acceptabele oplossing voor het Israëlisch-Palestijns conflict?
23
Moet euthanasie of hulp bij zelfdoding legaal zijn?
24
Leidt het verlagen van het federale vennootschapsbelastingtarief tot banencreatie?
26
Verbeteren gestandaardiseerde toetsen het onderwijs?
27
Moeten er meer wetten rondom wapenbezit worden ingevoerd?
28
Moet prostitutie legaal zijn?
29
Moet de overheid illegale immigranten toestaan om burgers te worden?
30
Moeten volwassenen het recht hebben om een verborgen vuurwapen te dragen?
31
Is obesitas een ziekte?
32
Verbeteren elektronische stemmachines het stemproces?
33
Moeten mensen vegetariër worden?
34
Zijn sociale netwerksites goed voor onze samenleving?
35
Dragen gewelddadige videogames bij aan geweld onder jongeren?
36
Is golf een sport?
37
Is mobiele telefoonstraling veilig?
38
Moet marihuana een medische optie zijn?
39
Moet het federale minimumloon worden verhoogd?
40
Moet de doodstraf worden toegestaan?
41
Moet het aflossen van studieschulden eenvoudiger worden gemaakt via faillissement?
42
Moet vechten toegestaan zijn in hockey?
43
Moet flessenwater verboden worden?
44
Moet de verkiezingsdag een nationale feestdag zijn?
45
Moet de cent in omloop blijven?
46
Moet netneutraliteit worden hersteld?
47
Is huiswerk nuttig?
48
Moet de stemgerechtigde leeftijd worden verlaagd?
49
Moeten politieagenten verplicht bodycams dragen?
50
Moet iedereen een basisinkomen krijgen?

Dataset Card for BEIR-NL Benchmark

Dataset Summary

BEIR-NL is a Dutch-translated version of the BEIR benchmark, a diverse and heterogeneous collection of datasets covering various domains from biomedical and financial texts to general web content. BEIR-NL contains the following tasks:

Languages

Dutch

Dataset Structure

BEIR-NL adheres to the structure of the original BEIR benchmark. All BEIR datasets must contain a corpus, queries and qrels (relevance judgments file). Qrels can be found in the BEIR repository on GitHub or Hugging Face. They format:

  • corpus file: a .jsonl file (jsonlines) that contains a list of dictionaries, each with three fields _id with unique document identifier, title with document title (optional) and text with document paragraph or passage. For example: {"_id": "doc1", "title": "Albert Einstein", "text": "Albert Einstein was een in Duitsland geboren..."}
  • queries file: a .jsonl file (jsonlines) that contains a list of dictionaries, each with two fields _id with unique query identifier and text with query text. For example: {"_id": "q1", "text": "Wie ontwikkelde de massa-energie-equivalentieformule?"}
  • qrels file: a .tsv file (tab-seperated) that contains three columns, i.e. the query-id, corpus-id and score in this order. Keep 1st row as header. For example: q1 doc1 1

Data Instances

A high level example of any beir dataset:

corpus = {
    "doc1": {
        "title": "Albert Einstein", 
        "text": (
            "Albert Einstein was een in Duitsland geboren theoretisch natuurkundige die de relativiteitstheorie ontwikkelde, "
            "een van de twee pijlers van de moderne natuurkunde (samen met de kwantummechanica). Zijn werk staat ook bekend "
            "om zijn invloed op de wetenschapfilosofie. Hij is bij het grote publiek vooral bekend vanwege zijn massa-energie- "
            "equivalentieformule E = mc^2, die 's werelds beroemdste vergelijking' wordt genoemd. Hij ontving in 1921 de Nobelprijs "
            "voor de Natuurkunde 'voor zijn verdiensten aan de theoretische natuurkunde, en in het bijzonder voor zijn ontdekking "
            "van de wet van het foto-elektrisch effect', een cruciale stap in de ontwikkeling van de kwantumtheorie."
        ),
    },
    "doc2": {
        "title": "", 
        "text": (
            "Tarwebier is een bovengistend bier dat wordt gebrouwen met een groot aandeel tarwe ten opzichte van de hoeveelheid "
            "gemoute gerst. De twee belangrijkste soorten zijn Duits Weißbier en Belgisch witbier; andere soorten zijn onder andere "
            "Lambiek (gemaakt met wilde gist), Berliner Weisse (een troebel, zuur bier) en Gose (een zuur, zout bier)."
        ),
    },
}

queries = {
    "q1": "Wie ontwikkelde de massa-energie-equivalentieformule?",
    "q2": "Welk bier wordt gebrouwen met een groot aandeel tarwe?"
}

qrels = {
    "q1": {"doc1": 1},
    "q2": {"doc2": 1},
}

Data Fields

Examples from all configurations have the following features:

Corpus

  • corpus: a dict feature representing the document title and passage text, made up of:
    • _id: a string feature representing the unique document id
      • title: a string feature, denoting the title of the document.
      • text: a string feature, denoting the text of the document.

Queries

  • queries: a dict feature representing the query, made up of:
    • _id: a string feature representing the unique query id
    • text: a string feature, denoting the text of the query.

Qrels

  • qrels: a dict feature representing the query document relevance judgements, made up of:
    • _id: a string feature representing the query id
      • _id: a string feature, denoting the document id.
      • score: a int32 feature, denoting the relevance judgement between query and document.

Data Splits

Dataset Website BEIR-Name Type Queries Corpus Rel D/Q BEIR BEIR-NL
TREC-COVID Homepage trec-covid test 50 171K 493.5 Link Link
NFCorpus Homepage nfcorpus train
dev
test
323 3.6K 38.2 Link Link
NQ Homepage nq train
test
3,452 2.68M 1.2 Link Link
HotpotQA Homepage hotpotqa train
dev
test
7,405 5.23M 2.0 Link Link
FiQA-2018 Homepage fiqa train
dev
test
648 57K 2.6 Link Link
ArguAna Homepage arguana test 1,406 8.67K 1.0 Link Link
Touche-2020 Homepage webis-touche2020 test 49 382K 19.0 Link Link
CQADupstack Homepage cqadupstack test 13,145 457K 1.4 Link Link
Quora Homepage quora dev
test
10,000 523K 1.6 Link Link
DBPedia Homepage dbpedia-entity dev
test
400 4.63M 38.2 Link Link
SCIDOCS Homepage scidocs test 1,000 25K 4.9 Link Link
FEVER Homepage fever train
dev
test
6,666 5.42M 1.2 Link Link
Climate-FEVER Homepage climate-fever test 1,535 5.42M 3.0 Link Link
SciFact Homepage scifact train
test
300 5K 1.1 Link Link

Dataset Creation

Curation Rationale

Zero-shot evaluation of information retrieval (IR) models is often performed using BEIR; a large and heterogeneous benchmark composed of multiple datasets, covering different retrieval tasks across various domains. Although BEIR has become a standard benchmark for the zero-shot setup, its exclusively English content reduces its utility for underrepresented languages in IR, including Dutch. To address this limitation and encourage the development of Dutch IR models, we introduce BEIR-NL by automatically translating the publicly accessible BEIR datasets into Dutch.

Source Data

BEIR repository on GitHub.

Annotations

We prompted Gemini-1.5-flash to translate BEIR into Dutch. A small portion of translations were done using GPT-4o-mini and Google Translate, as Gemini declined to translate certain content and had occasional issues with tags in prompts.

Considerations for Using the Data

Other Known Limitations

Not Native Dutch Resources. While BEIR-NL provides a benchmark for evaluating IR models in Dutch, it relies on translations from the original BEIR, which is exclusively in English. This lack of native Dutch datasets limits the ability of BEIR-NL to fully represent and reflect the linguistic nuances and cultural context of the language, and therefore, the complexities of Dutch IR, especially in domain-specific contexts with local terminology and knowledge.

Data Contamination. Many modern IR models are trained on massive corpora that might include content from BEIR. This can result in inflated performances --as models might have already seen the relevant data during different phases of training-- raising concerns about the validity of zero-shot evaluations. Ensuring a truly zero-shot evaluation is a difficult challenge, as many IR models lack transparency regarding the exact composition of training corpora.

Benchmark Validity Over Time. BEIR has become a standard benchmark to evaluate the performance of IR models, attracting a large number of evaluations over time. This extensive usage introduces the risk of overfitting, as researchers might unintentionally train models tailored to perform well on BEIR rather than on broader IR tasks. In addition, advances in IR models and evaluation needs might outpace the benchmark, making it less representative and less relevant. As a result, the relevance and validity of BEIR as well as BEIR-NL may diminish over time.

Additional Information

Licensing Information

This subset (Touche-2020) of BEIR-NL is licensed under the CC BY-NC-SA 4.0 license.

Citation Information

If you find BEIR-NL useful in your research, please consider citing it, as well as the original BEIR benchmark it is derived from:

@misc{banar2024beirnlzeroshotinformationretrieval,
    title={BEIR-NL: Zero-shot Information Retrieval Benchmark for the Dutch Language}, 
     author={Nikolay Banar and Ehsan Lotfi and Walter Daelemans},
     year={2024},
     eprint={2412.08329},
     archivePrefix={arXiv},
     primaryClass={cs.CL},
     url={https://arxiv.org/abs/2412.08329}, 
}

@inproceedings{thakur2021beir,
    title={{BEIR}: A Heterogeneous Benchmark for Zero-shot Evaluation of Information Retrieval Models},
    author={Nandan Thakur and Nils Reimers and Andreas R{\"u}ckl{\'e} and Abhishek Srivastava and Iryna Gurevych},
    booktitle={Thirty-fifth Conference on Neural Information Processing Systems Datasets and Benchmarks Track (Round 2)},
    year={2021},
    url={https://openreview.net/forum?id=wCu6T5xFjeJ}
}
Downloads last month
25

Collection including clips/beir-nl-webis-touche2020