Bram Vanroy
commited on
Commit
•
172dde4
1
Parent(s):
8a10664
add CI disclaimer
Browse files- content.py +3 -1
content.py
CHANGED
@@ -21,7 +21,9 @@ DISCLAIMER = """## Disclaimer
|
|
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 |
-
|
|
|
|
|
25 |
If you have any suggestions for other Dutch benchmarks, please [let me know](https://twitter.com/BramVanroy) so I can add them!
|
26 |
"""
|
27 |
|
|
|
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 |
+
|
25 |
+
Another shortcoming is that we do not calculate significancy scores or confidence intervals. When results are close together in the leaderboard I therefore urge caution when interpreting the model ranks.
|
26 |
+
|
27 |
If you have any suggestions for other Dutch benchmarks, please [let me know](https://twitter.com/BramVanroy) so I can add them!
|
28 |
"""
|
29 |
|