Repository navigation
dataset: use v2 GermanGovService retrieval data - #5323
Merged
Samoed merged 1 commit intoAug 29, 2026
Merged
Conversation
Collaborator
|
Can you run evaluation on some model which already has results on these task and compare results, just to check these is not causing any regression in results |
Contributor
Author
|
Thanks, I ran a regression check with an existing results model.
So the v2 dataset switch does not appear to introduce a result regression for this task/model. |
Collaborator
|
LGTM ! |
Samoed
approved these changes
Aug 29, 2026
Member
|
This dataset uploaded with |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
GermanGovServiceRetrieval is listed in #3424 as a retrieval task that still uses the old custom loading path. The dataset has already been re-uploaded under the MTEB organization with the standard corpus, queries, and qrels configs.
Refs #3424.
What changed
mteb/GermanGovServiceRetrievalat revisiona6cf81304bf8b82d5497a0f7ad9e08399b8f27d3.load_data()implementation.Validation
it-at-m/LHM-Dienstleistungen-QA@ed40131b56ce86ce3666f2942953595dd9d29608and compared them withmteb/GermanGovServiceRetrieval@a6cf81304bf8b82d5497a0f7ad9e08399b8f27d3: corpus, queries, and qrels match exactly (105 corpus docs, 356 queries, 356 qrels).RetrievalDatasetLoader: 105 corpus docs, 356 queries, 356 qrels, no qrels pointing to missing query or corpus IDs.python -m py_compile mteb\tasks\retrieval\deu\german_gov_service_retrieval.py.venv\Scripts\ruff.exe check mteb\tasks\retrieval\deu\german_gov_service_retrieval.pygit diff --checkRisk / follow-up
Low. This changes only one German retrieval task to use the verified MTEB-hosted v2 dataset. Follow-up remains for other retrieval tasks in #3424.