--- configs: - config_name: bm25 data_files: - split: NanoArguAna path: bm25/NanoArguAna.parquet - split: NanoClimateFEVER path: bm25/NanoClimateFEVER.parquet - split: NanoDBPedia path: bm25/NanoDBPedia.parquet - split: NanoFEVER path: bm25/NanoFEVER.parquet - split: NanoFiQA2018 path: bm25/NanoFiQA2018.parquet - split: NanoHotpotQA path: bm25/NanoHotpotQA.parquet - split: NanoMSMARCO path: bm25/NanoMSMARCO.parquet - split: NanoNFCorpus path: bm25/NanoNFCorpus.parquet - split: NanoNQ path: bm25/NanoNQ.parquet - split: NanoQuoraRetrieval path: bm25/NanoQuoraRetrieval.parquet - split: NanoSCIDOCS path: bm25/NanoSCIDOCS.parquet - split: NanoSciFact path: bm25/NanoSciFact.parquet - split: NanoTouche2020 path: bm25/NanoTouche2020.parquet - config_name: corpus data_files: - split: NanoArguAna path: corpus/NanoArguAna-* - split: NanoClimateFEVER path: corpus/NanoClimateFEVER-* - split: NanoDBPedia path: corpus/NanoDBPedia-* - split: NanoFEVER path: corpus/NanoFEVER-* - split: NanoFiQA2018 path: corpus/NanoFiQA2018-* - split: NanoHotpotQA path: corpus/NanoHotpotQA-* - split: NanoMSMARCO path: corpus/NanoMSMARCO-* - split: NanoNFCorpus path: corpus/NanoNFCorpus-* - split: NanoNQ path: corpus/NanoNQ-* - split: NanoQuoraRetrieval path: corpus/NanoQuoraRetrieval-* - split: NanoSCIDOCS path: corpus/NanoSCIDOCS-* - split: NanoSciFact path: corpus/NanoSciFact-* - split: NanoTouche2020 path: corpus/NanoTouche2020-* - config_name: qrels data_files: - split: NanoArguAna path: qrels/NanoArguAna.parquet - split: NanoClimateFEVER path: qrels/NanoClimateFEVER.parquet - split: NanoDBPedia path: qrels/NanoDBPedia.parquet - split: NanoFEVER path: qrels/NanoFEVER.parquet - split: NanoFiQA2018 path: qrels/NanoFiQA2018.parquet - split: NanoHotpotQA path: qrels/NanoHotpotQA.parquet - split: NanoMSMARCO path: qrels/NanoMSMARCO.parquet - split: NanoNFCorpus path: qrels/NanoNFCorpus.parquet - split: NanoNQ path: qrels/NanoNQ.parquet - split: NanoQuoraRetrieval path: qrels/NanoQuoraRetrieval.parquet - split: NanoSCIDOCS path: qrels/NanoSCIDOCS.parquet - split: NanoSciFact path: qrels/NanoSciFact.parquet - split: NanoTouche2020 path: qrels/NanoTouche2020.parquet - config_name: queries data_files: - split: NanoArguAna path: queries/NanoArguAna.parquet - split: NanoClimateFEVER path: queries/NanoClimateFEVER.parquet - split: NanoDBPedia path: queries/NanoDBPedia.parquet - split: NanoFEVER path: queries/NanoFEVER.parquet - split: NanoFiQA2018 path: queries/NanoFiQA2018.parquet - split: NanoHotpotQA path: queries/NanoHotpotQA.parquet - split: NanoMSMARCO path: queries/NanoMSMARCO.parquet - split: NanoNFCorpus path: queries/NanoNFCorpus.parquet - split: NanoNQ path: queries/NanoNQ.parquet - split: NanoQuoraRetrieval path: queries/NanoQuoraRetrieval.parquet - split: NanoSCIDOCS path: queries/NanoSCIDOCS.parquet - split: NanoSciFact path: queries/NanoSciFact.parquet - split: NanoTouche2020 path: queries/NanoTouche2020.parquet default: true language: - multilingual tags: - information-retrieval - retrieval - nano - bm25 - hakari-bench dataset_info: config_name: corpus features: - name: _id dtype: string - name: text dtype: string splits: - name: NanoArguAna num_bytes: 3854759 num_examples: 3635 - name: NanoClimateFEVER num_bytes: 5513610 num_examples: 3408 - name: NanoDBPedia num_bytes: 2333296 num_examples: 6045 - name: NanoFEVER num_bytes: 6185496 num_examples: 4996 - name: NanoFiQA2018 num_bytes: 4387013 num_examples: 4598 - name: NanoHotpotQA num_bytes: 1921151 num_examples: 5090 - name: NanoMSMARCO num_bytes: 1789614 num_examples: 5043 - name: NanoNFCorpus num_bytes: 4645636 num_examples: 2953 - name: NanoNQ num_bytes: 2739595 num_examples: 5035 - name: NanoQuoraRetrieval num_bytes: 371210 num_examples: 5046 - name: NanoSCIDOCS num_bytes: 2244517 num_examples: 2210 - name: NanoSciFact num_bytes: 4322717 num_examples: 2919 - name: NanoTouche2020 num_bytes: 12647783 num_examples: 5745 download_size: 33326387 dataset_size: 52956397 --- # NanoBEIR-sr This dataset is a Nano-style retrieval dataset. Nano-series evaluation can be run easily with [HAKARI-Bench](https://github.com/hotchpotch/hakari-bench). NanoBEIR-sr is derived from MNanoBEIR / NanoBEIR. It follows the Hugging Face Datasets layout convention used by [sentence-transformers/NanoBEIR-en](https://huggingface.co/datasets/sentence-transformers/NanoBEIR-en): each Nano split has separate `corpus`, `queries`, and `qrels` tables, and BM25 candidates are provided separately in a `bm25` table. This layout follows the NanoBEIR-style evaluation approach summarized in [NanoBEIR](https://huggingface.co/blog/sionic-ai/eval-sionic-nano-beir). NanoBEIR-sr is the Serbian language-specific component of MNanoBEIR. It groups compact BEIR-derived retrieval tasks for efficient evaluation of document ranking in that language. ## Source Links - Final dataset: [hakari-bench/NanoBEIR-sr](https://huggingface.co/datasets/hakari-bench/NanoBEIR-sr) ## Data Layout This dataset uses four Hugging Face Datasets configs: - `corpus`: documents with `_id` and `text` - `queries`: queries with `_id` and `text` - `qrels`: positive relevance labels with `query-id` and `corpus-id` - `bm25`: BM25 candidate lists with `query-id` and `corpus-ids` Each config has the same Nano split names. The `qrels` config is positive-only. Source rows with `score <= 0` are treated as non-relevant or hard-negative annotations and are not included in `qrels`. When the source provides such rows, their documents are preferentially used as hard negatives in the `corpus` config before generic corpus-fill documents. Source hard negatives are sampled deterministically with query round-robin so one query's negative pool does not dominate the corpus. ## Split Statistics Length statistics are computed with `len(str(text))` over the `queries` and `corpus` tables. `std` is the population standard deviation over the rows in each split. | Nano split | Queries | Corpus | Qrels | Query avg | Query std | Query median | Query p25 | Query p75 | Doc avg | Doc std | Doc median | Doc p25 | Doc p75 | |---|---:|---:|---:|---:|---:|---:|---:|---:|---:|---:|---:|---:|---:| | NanoArguAna | 50 | 3635 | 50 | 1182.9 | 400.3 | 1210.0 | 904.2 | 1432.2 | 989.8 | 553.5 | 885.0 | 604.0 | 1235.0 | | NanoClimateFEVER | 50 | 3408 | 148 | 135.2 | 53.5 | 129.5 | 98.5 | 172.8 | 1552.3 | 850.6 | 1403.0 | 940.0 | 1994.0 | | NanoDBPedia | 50 | 6045 | 1158 | 41.2 | 64.2 | 31.5 | 20.0 | 43.0 | 338.9 | 143.2 | 369.0 | 237.0 | 444.0 | | NanoFEVER | 50 | 4996 | 57 | 46.1 | 16.6 | 44.0 | 36.2 | 52.5 | 1184.6 | 826.4 | 1007.5 | 586.0 | 1580.0 | | NanoFiQA2018 | 50 | 4598 | 123 | 63.8 | 23.1 | 60.5 | 45.2 | 80.2 | 914.4 | 865.2 | 661.0 | 360.0 | 1159.8 | | NanoHotpotQA | 50 | 5090 | 100 | 86.5 | 34.7 | 75.5 | 56.8 | 105.0 | 353.6 | 250.0 | 306.0 | 159.0 | 486.0 | | NanoMSMARCO | 50 | 5043 | 50 | 35.6 | 18.0 | 32.0 | 25.2 | 43.8 | 331.1 | 131.3 | 300.0 | 246.0 | 382.0 | | NanoNFCorpus | 50 | 2953 | 1651 | 23.1 | 16.9 | 20.0 | 8.2 | 33.5 | 1522.7 | 546.3 | 1540.0 | 1204.0 | 1791.0 | | NanoNQ | 50 | 5035 | 57 | 45.6 | 13.0 | 44.5 | 37.0 | 53.8 | 514.5 | 422.4 | 436.0 | 177.0 | 738.5 | | NanoQuoraRetrieval | 50 | 5046 | 70 | 49.3 | 19.4 | 45.0 | 38.0 | 54.8 | 58.1 | 41.6 | 49.0 | 37.0 | 67.0 | | NanoSCIDOCS | 50 | 2210 | 244 | 77.1 | 20.6 | 74.0 | 62.2 | 89.5 | 944.5 | 686.6 | 919.0 | 578.2 | 1236.5 | | NanoSciFact | 50 | 2919 | 56 | 96.4 | 45.3 | 90.0 | 58.0 | 126.0 | 1433.9 | 612.7 | 1341.0 | 1040.0 | 1734.0 | | NanoTouche2020 | 49 | 5745 | 932 | 55.1 | 14.5 | 55.0 | 45.0 | 66.0 | 2095.8 | 2477.9 | 977.0 | 322.0 | 2967.0 | ## Construction Steps This dataset is constructed as follows. 1. Use MNanoBEIR / NanoBEIR as the upstream benchmark or dataset family. 2. Load source datasets from the `hakari-bench/NanoBEIR-sr` corpus, queries, and qrels tables. 3. Source evaluation split policy: the NanoBEIR split set. 4. Create one Nano split for each selected source retrieval task. 5. Keep up to 200 eligible queries per Nano split. 6. Treat source relevance rows with `score > 0` as qrels-positive documents. If the source has no score column, treat its qrels as positive-only only when that is the source task convention. 7. Exclude source rows with `score <= 0` from `qrels`. When such rows are available for selected queries, use their documents as hard-negative corpus candidates before generic fill documents. 8. Include all qrels-positive documents for the selected queries. 9. Use the included corpus tables for each Nano split; no additional document resampling is performed. 10. Remove exact duplicate query text and document text within each split. If a removed document duplicate was referenced by qrels, the qrels row was removed. 11. Store corpus text as `title` plus body text when available. 12. Generate BM25 top-100 candidates with `regex` tokenization. 13. If a qrels-positive document is missing from the raw BM25 result, insert it into the final `bm25` candidate list by replacing a tail non-positive candidate. The `qrels` config is positive-only. When needed for top-k reranking coverage, positive qrels are capped per query to the BM25 top-k. The `bm25` candidate subset is generated from the included corpus for each split. For top-100 reranking diagnostics, positive qrels are capped to at most 100 documents per query before BM25 positive forcing. This makes full relevant coverage possible for splits whose upstream qrels contain more than 100 positives for a single query. ## BM25 Subset Policy The `bm25` config is a candidate subset for first-stage retrieval and reranking. It is not a separate source dataset. Each row contains one query id and a ranked list of up to 100 corpus ids. BM25 candidates are generated from the selected corpus for each split. When a qrels-positive document is not present in the raw BM25 top-100 results, the missing positive is forced into the final candidate list by replacing a tail candidate that is not positive for that query. Candidate ids are kept unique after replacement. Concretely, each `bm25` row is produced by tokenizing the selected split corpus and query texts with `regex`, ranking the corpus with BM25, then writing the ranked corpus ids as `corpus-ids` for that query. The list is a candidate subset for downstream evaluation, not a full-corpus ranking. Source hard negatives, including documents referenced by source rows with `score <= 0`, may appear in the selected corpus and can naturally appear in BM25 candidates. They are still non-relevant and are not listed in `qrels`. When source hard negatives are available, the default corpus sampling policy is query round-robin: group hard negatives by selected query, preserve source rank/order within each query, add at most one new hard negative from each query per pass, remove duplicate IDs and exact duplicate text, then fill any remaining slots from source corpus order. ## Split Mapping Each Nano split maps to one source retrieval task unless noted otherwise. | Nano split | Source task | Source dataset | Queries | Corpus | Qrels | |---|---|---|---:|---:|---:| | NanoArguAna | NanoArguAna | [hakari-bench/NanoBEIR-sr](https://huggingface.co/datasets/hakari-bench/NanoBEIR-sr) | 50 | 3635 | 50 | | NanoClimateFEVER | NanoClimateFEVER | [hakari-bench/NanoBEIR-sr](https://huggingface.co/datasets/hakari-bench/NanoBEIR-sr) | 50 | 3408 | 148 | | NanoDBPedia | NanoDBPedia | [hakari-bench/NanoBEIR-sr](https://huggingface.co/datasets/hakari-bench/NanoBEIR-sr) | 50 | 6045 | 1158 | | NanoFEVER | NanoFEVER | [hakari-bench/NanoBEIR-sr](https://huggingface.co/datasets/hakari-bench/NanoBEIR-sr) | 50 | 4996 | 57 | | NanoFiQA2018 | NanoFiQA2018 | [hakari-bench/NanoBEIR-sr](https://huggingface.co/datasets/hakari-bench/NanoBEIR-sr) | 50 | 4598 | 123 | | NanoHotpotQA | NanoHotpotQA | [hakari-bench/NanoBEIR-sr](https://huggingface.co/datasets/hakari-bench/NanoBEIR-sr) | 50 | 5090 | 100 | | NanoMSMARCO | NanoMSMARCO | [hakari-bench/NanoBEIR-sr](https://huggingface.co/datasets/hakari-bench/NanoBEIR-sr) | 50 | 5043 | 50 | | NanoNFCorpus | NanoNFCorpus | [hakari-bench/NanoBEIR-sr](https://huggingface.co/datasets/hakari-bench/NanoBEIR-sr) | 50 | 2953 | 1651 | | NanoNQ | NanoNQ | [hakari-bench/NanoBEIR-sr](https://huggingface.co/datasets/hakari-bench/NanoBEIR-sr) | 50 | 5035 | 57 | | NanoQuoraRetrieval | NanoQuoraRetrieval | [hakari-bench/NanoBEIR-sr](https://huggingface.co/datasets/hakari-bench/NanoBEIR-sr) | 50 | 5046 | 70 | | NanoSCIDOCS | NanoSCIDOCS | [hakari-bench/NanoBEIR-sr](https://huggingface.co/datasets/hakari-bench/NanoBEIR-sr) | 50 | 2210 | 244 | | NanoSciFact | NanoSciFact | [hakari-bench/NanoBEIR-sr](https://huggingface.co/datasets/hakari-bench/NanoBEIR-sr) | 50 | 2919 | 56 | | NanoTouche2020 | NanoTouche2020 | [hakari-bench/NanoBEIR-sr](https://huggingface.co/datasets/hakari-bench/NanoBEIR-sr) | 49 | 5745 | 932 | ## BM25 nDCG@10 `nDCG@10` is computed from the included BM25 ranking against the included qrels. Coverage is measured against included qrels at the same BM25 top-k used for reranking diagnostics. The included BM25 candidate subset has 100.00% query coverage and 100.00% relevant coverage for every split. | Nano split | Tokenizer | Forced BM25 positives | Query cov | Relevant cov | BM25 nDCG@10 | |---|---|---:|---:|---:|---:| | NanoArguAna | regex | 8 | 100.00% | 100.00% | 0.2817 | | NanoClimateFEVER | regex | 67 | 100.00% | 100.00% | 0.2389 | | NanoDBPedia | regex | 580 | 100.00% | 100.00% | 0.4341 | | NanoFEVER | regex | 8 | 100.00% | 100.00% | 0.6486 | | NanoFiQA2018 | regex | 62 | 100.00% | 100.00% | 0.1904 | | NanoHotpotQA | regex | 13 | 100.00% | 100.00% | 0.6327 | | NanoMSMARCO | regex | 12 | 100.00% | 100.00% | 0.2833 | | NanoNFCorpus | regex | 1498 | 100.00% | 100.00% | 0.2342 | | NanoNQ | regex | 15 | 100.00% | 100.00% | 0.2624 | | NanoQuoraRetrieval | regex | 6 | 100.00% | 100.00% | 0.5964 | | NanoSCIDOCS | regex | 126 | 100.00% | 100.00% | 0.2561 | | NanoSciFact | regex | 7 | 100.00% | 100.00% | 0.6468 | | NanoTouche2020 | regex | 308 | 100.00% | 100.00% | 0.4741 | ## Skipped Tasks No source tasks were skipped. ## License NanoBEIR-sr is a derived dataset. Users must comply with the licenses, terms, and attribution requirements of the upstream source datasets.