[Evals] Add eval for Dhivehi diacritical marks #1495
+12
−0
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.
Thank you for contributing an eval!♥️
🚨 Please make sure your PR follows these guidelines, failure to follow the guidelines below will result in the PR being closed automatically. Note that even if the criteria are met, that does not guarantee the PR will be merged nor GPT-4 access be granted. 🚨
PLEASE READ THIS:
In order for a PR to be merged, it must fail on GPT-4. We are aware that right now, users do not have access, so you will not be able to tell if the eval fails or not. Please run your eval with GPT-3.5-Turbo, but keep in mind as we run the eval, if GPT-4 gets higher than 90% on the eval, we will likely reject it since GPT-4 is already capable of completing the task.
We plan to roll out a way for users submitting evals to see the eval performance on GPT-4 soon. Stay tuned! Until then, you will not be able to see the eval performance on GPT-4. Starting April 10, the minimum eval count is 15 samples, we hope this makes it easier to create and contribute evals.
Also, please note that we're using Git LFS for storing the JSON files, so please make sure that you move the JSON file to Git LFS before submitting a PR. Details on how to use Git LFS are available here.
Eval details 📑
Eval name
dhivehi-diacriticals
Eval description
Given a Dhivehi sentence that includes a word missing its diacritical marks, deduce the appropriate diacritical marks for that word and output the word with correct diacritical marks.
What makes this a useful eval?
Dhivehi [1] is the Maldivian language, spoken primarily in the Maldives. It is written from right to left using Thaana [2] with vowels expressed as diacritics and consonants written on different lines. Twenty four symbols of the Thaana alphabet make up the consonants of the script [3]. There are eleven diacritics used along with the consonants. An extension of the Thaana script referred to as dotted/thikijehi Thaana [4] made up of fourteen characters is also used to transliterate Perso-Arabic script.
Consider the following sentence in Dhivehi: "މިޑްޓާމް ބަންދަށްފަހު އަލުން ސްކޫލުތަކުގެ ކިޔެވުން ފަށައިފިއެވެ" (meaning in English: Schools re-opened after midterm holidays.). In this eval, we provide the model with "މިޑްޓާމް ބަންދަށްފަހު އަލުން ސކލތކގ ކިޔެވުން ފަށައިފިއެވެ" and ask it to predict the word " ސްކޫލުތަކުގެ " with the diacritical marks.
To list a few, this eval will help evaluate the language models':
(i) robustness and adaptability to diverse linguistic systems such as those making use of right to left writing systems (specifically Dhivehi in this case)
(ii) ability to understand the phonetic and morphological properties of Dhivehi
Note: Data is from the Common Voice repo
data/dv/dv_questions.txt
[5]. As such, it is available under the CC0 public domain Creative Commons license [6].References
[1] https://en.wikipedia.org/wiki/Maldivian_language
[2] https://en.wikipedia.org/wiki/Thaana
[3] https://en.wikipedia.org/wiki/Thaana#Consonants
[4] https://en.wikipedia.org/wiki/Thaana#Thikijehi_Thaana
[5] https://github.com/common-voice/common-voice/blob/main/server/data/dv/dv_questions.txt
[6] https://github.com/common-voice/common-voice/tree/main?tab=readme-ov-file#licensing-and-content-source
Criteria for a good eval ✅
Below are some of the criteria we look for in a good eval. In general, we are seeking cases where the model does not do a good job despite being capable of generating a good response (note that there are some things large language models cannot do, so those would not make good evals).
Your eval should be:
Basic
evals or theFact
Model-graded eval, or an exhaustive rubric for evaluating answers for theCriteria
Model-graded eval.If there is anything else that makes your eval worth including, please document it below.
Unique eval value
Dhivehi is a less commonly studied language, and incorporating it into evaluations promotes linguistic diversity and inclusivity. It tests the model's capacity to learn and perform well on languages with fewer resources and less representation in the digital world, which is crucial for creating equitable AI systems.
Eval structure 🏗️
Your eval should
evals/registry/data/{name}
evals/registry/evals/{name}.yaml
(For now, we will only be approving evals that use one of the existing eval classes. You may still write custom eval classes for your own cases, and we may consider merging them in the future.)
Final checklist 👀
Submission agreement
By contributing to Evals, you are agreeing to make your evaluation logic and data under the same MIT license as this repository. You must have adequate rights to upload any data used in an Eval. OpenAI reserves the right to use this data in future service improvements to our product. Contributions to OpenAI Evals will be subject to our usual Usage Policies (https://platform.openai.com/docs/usage-policies).
Email address validation
If your submission is accepted, we will be granting GPT-4 access to a limited number of contributors. Access will be given to the email address associated with the commits on the merged pull request.
Limited availability acknowledgment
We know that you might be excited to contribute to OpenAI's mission, help improve our models, and gain access to GPT-4. However, due to the requirements mentioned above and the high volume of submissions, we will not be able to accept all submissions and thus not grant everyone who opens a PR GPT-4 access. We know this is disappointing, but we hope to set the right expectation before you open this PR.
Submit eval
pip install pre-commit; pre-commit install
and have verified thatmypy
,black
,isort
,autoflake
andruff
are running when I commit and pushFailure to fill out all required fields will result in the PR being closed.
Eval JSON data
Since we are using Git LFS, we are asking eval submitters to add in as many Eval Samples (at least 5) from their contribution here:
View evals in JSON
Eval