BramVanroy commited on
Commit
78dad7b
1 Parent(s): 89b5433

Update content.py

Browse files
Files changed (1) hide show
  1. content.py +3 -1
content.py CHANGED
@@ -18,7 +18,9 @@ I did not verify their translations and I do not maintain the datasets, I only r
18
 
19
  DISCLAIMER = """## Disclaimer
20
 
21
- I did not verify the (translation) quality of the benchmarks. If you encounter issues with the benchmark contents, please contact the original authors.
 
 
22
 
23
  I am aware that benchmarking models on *translated* data is not ideal. However, for Dutch there are no other options for generative models at the moment. Because the benchmarks were automatically translated, some translationese effects may occur: the translations may not be fluent Dutch or still contain artifacts of the source text (like word order, literal translation, certain vocabulary items). Because of that, an unfair advantage may be given to the non-Dutch models: Dutch is closely related to English, so if the benchmarks are in automatically translated Dutch that still has English properties, those English models may not have too many issues with that. If the benchmarks were to have been manually translated or, even better, created from scratch in Dutch, those non-Dutch models may have a harder time. Maybe not. We cannot know for sure until we have high-quality, manually crafted benchmarks for Dutch.
24
 
 
18
 
19
  DISCLAIMER = """## Disclaimer
20
 
21
+ **Evaluating generative models.** Counter-intuitively, we often evaluate generative models with multiple choice questions (as done here). This is useful to gauge the reasoning capabilities of LLMs. However, they do not account for the user experience, including how fluent and natural the text is. A prime example is how top models such as Zephyr, Mistral and Mixtral are actually quite poor when using them as a chatbot for Dutch. But they appear to be good at at least "understanding" a task in Dutch and correctly reasoning about it. Similarly, for humans understanding the general gist of a (new) written language (like after a few months on Duolingo) is something completely different from writing an eloquent, native-level article. This is an under-researched part of evaluating LLMs, especially in non-English languages.
22
+
23
+ **Translations of benchmarks.** I did not verify the (translation) quality of the benchmarks. If you encounter issues with the benchmark contents, please contact the original authors.
24
 
25
  I am aware that benchmarking models on *translated* data is not ideal. However, for Dutch there are no other options for generative models at the moment. Because the benchmarks were automatically translated, some translationese effects may occur: the translations may not be fluent Dutch or still contain artifacts of the source text (like word order, literal translation, certain vocabulary items). Because of that, an unfair advantage may be given to the non-Dutch models: Dutch is closely related to English, so if the benchmarks are in automatically translated Dutch that still has English properties, those English models may not have too many issues with that. If the benchmarks were to have been manually translated or, even better, created from scratch in Dutch, those non-Dutch models may have a harder time. Maybe not. We cannot know for sure until we have high-quality, manually crafted benchmarks for Dutch.
26