Add `decrypt-vigenere-cipher` eval
Eval details đź“‘
Eval name
decrypt-vigenere-cipher
Eval description
Test the models ability to decrypt with the Vigenère cipher.
What makes this a useful eval?
By testing a language model's ability to use Vigenère cipher we can evaluate the model's ability apply a cryptographic procedure, and recognize patterns required to decrypt a ciphertext. Additionally, since the Vigenère cipher has been a popular encryption method for centuries, it could ensure effectiveness in decoding historical documents or other text encrypted with classical ciphers.
Note: Others in the community have shown interest in this kind of evaluation with #58 and #62.
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:
- [x] Thematically consistent: The eval should be thematically consistent. We'd like to see a number of prompts all demonstrating some particular failure mode. For example, we can create an eval on cases where the model fails to reason about the physical world.
- [x] Contains failures where a human can do the task, but either GPT-4 or GPT-3.5-Turbo could not.
- [x] Includes good signal around what is the right behavior. This means either a correct answer for
Basicevals or theFactModel-graded eval, or an exhaustive rubric for evaluating answers for theCriteriaModel-graded eval. - [x] Include at least 100 high quality examples (it is okay to only contribute 5-10 meaningful examples and have us test them with GPT-4 before adding all 100)
If there is anything else that makes your eval worth including, please document it below.
Unique eval value
Insert what makes your eval high quality that was not mentioned above. (Not required)
Eval structure 🏗️
Your eval should
- [x] Check that your data is in
evals/registry/data/{name} - [x] Check that your yaml is registered at
evals/registry/evals/{name}.jsonl - [x] Ensure you have the right to use the data you submit via this eval
(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).
- [x] I agree that my submission will be made available under an MIT license and complies with OpenAI's 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 merged pull request.
- [x] I acknowledge that GPT-4 access will only be granted, if applicable, to the email address used for my merged pull request.
Limited availability acknowledgement
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 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.
- [x] I understand that opening a PR, even if it meets the requirements above, does not guarantee the PR will be merged nor GPT-4 access granted.
Submit eval
- [x] I have filled out all required fields in the evals PR form
- [x] (Ignore if not submitting code) I have run
pip install pre-commit; pre-commit installand have verified thatblack,isort, andautoflakeare running when I commit and push
Failure 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
{"input": [{"role": "system", "content": "You will be given a Vigenère cipher, only reply with the deciphered plaintext using the key 'goodbyemoon'"}, {"role": "user", "content": "nszopusdzr"}], "ideal": "helloworld"}
{"input": [{"role": "system", "content": "You will be given a Vigenère cipher, only reply with the deciphered plaintext using the key 'ABCDABCDABCDABCDABCDABCDABCD'"}, {"role": "user", "content": "CSASTPKVSIQUTGQUCSASTPIUAQJB"}], "ideal": "cryptoisshortforcryptography"}
{"input": [{"role": "system", "content": "You will be given a Vigenère cipher, only reply with the deciphered plaintext using the key 'Polyphia'"}, {"role": "user", "content": "Lvppt kw ydi hyca bo vc qmg scnrv?"}], "ideal": "Where do you want to go for lunch?"}
{"input": [{"role": "system", "content": "You will be given a Vigenère cipher, only reply with the deciphered plaintext using the key 'AGI'"}, {"role": "user", "content": "Tnm fabuxm"}], "ideal": "The future"}
{"input": [{"role": "system", "content": "You will be given a Vigenère cipher, only reply with the deciphered plaintext using the key 'THATFEELING'"}, {"role": "user", "content": "B'ce ejevymq zaht ijstwm joes fhwkie eugm fon xemo, xruise pnpp qwemxa wafx czc qow, ium uisatr cbsl gjzic nbxzlt ata czc zgwl tajq jpmy."}], "ideal": "I've learned that people will forget what you said, people will forget what you did, but people will never forget how you made them feel."}
Include at least 100 high quality examples (it is okay to only contribute 5-10 meaningful examples and have us test them with GPT-4 before adding all 100)
To expand on this requirement: I would be happy to generate the 100 high quality examples if required. Following #1, I added 11 of what I thought could be considered high-quality examples of some variety including unique ciphers and ones found on the Wikipedia page.
Currently with gpt-3.5-turbo, it doesn't do so well with an accuracy of 0.09:
$ oaieval gpt-3.5-turbo decrypt-vigenere-cipher
...
[2023-03-16 01:42:57,349] [data.py:78] Fetching decrypt_vigenere_cipher/samples.jsonl
[2023-03-16 01:42:57,351] [eval.py:30] Evaluating 11 samples
...
[2023-03-16 01:42:59,610] [record.py:320] Final report: {'accuracy': 0.09090909090909091}. Logged to /tmp/evallogs/230316014257QEIYTHGW_gpt-3.5-turbo_decrypt-vigenere-cipher.jsonl
[2023-03-16 01:42:59,610] [oaieval.py:209] Final report:
[2023-03-16 01:42:59,610] [oaieval.py:211] accuracy: 0.09090909090909091
[2023-03-16 01:42:59,613] [record.py:309] Logged 33 rows of events to /tmp/evallogs/230316014257QEIYTHGW_gpt-3.5-turbo_decrypt-vigenere-cipher.jsonl: insert_time=2.825ms
Interestingly, the chat log reveals some fun insights for myself:
-
It seems to have memorized(?) the example from the Wikipedia page:
{ "run_id": "230316014328NHVXA7G4", "event_id": 29, "sample_id": "decrypt-vigenere-cipher.dev.2", "type": "sampling", "data": { "prompt": [ { "role": "system", "content": "You will be given a Vigenère cipher, only reply with the deciphered plaintext using the key 'LIONLIONLIONLIONLIONLIONLIONLIONLIO'" }, { "role": "user", "content": "epsdfqqxmzcjynckucacdwjrcbvrwinlowu" } ], "sampled": "thequickbrownfoxjumpsoverthelazydog", "options": [ "thequickbrownfoxjumpsoverthelazydog" ], "picked": "thequickbrownfoxjumpsoverthelazydog", "expected": [ "thequickbrownfoxjumpsoverthelazydog" ], "match": true, "metadata": { "completion_id": "chatcmpl-6uWwS39hTVTXSFBT0zK2TqIREptPn", "model": "gpt-3.5-turbo-0301" } }, "created_by": "", "created_at": "2023-03-16 01:43:37.135421+00:00" } -
But it couldn't apply a simple-ish short cipher:
{ "run_id": "230316014328NHVXA7G4", "event_id": 25, "sample_id": "decrypt-vigenere-cipher.dev.9", "type": "sampling", "data": { "prompt": [ { "role": "system", "content": "You will be given a Vigenère cipher, only reply with the deciphered plaintext using the key 'AGI'" }, { "role": "user", "content": "Tnm fabuxm" } ], "sampled": "The plaintext is \"Our world\".", "options": [ "The future" ], "picked": null, "expected": [ "The future" ], "match": false, "metadata": { "completion_id": "chatcmpl-6uWwKJgGumWWp8UKcSeKXpawMB2Bp", "model": "gpt-3.5-turbo-0301" } }, "created_by": "", "created_at": "2023-03-16 01:43:33.358107+00:00" }
I used CyberChef to generate and validate my examples:
Thanks for opening this PR, Character-level reasoning and operations are a well-known failure mode of the model due to a common underlying issue in LLMs. In its current form, this eval does not seem to expose any new gaps in our understanding of model performance. We also know that this could be solved by giving the model a code interpreter. Model very well knows how to write code to solve this problem, and that code can be fed to the code interpreter to get the correct answer.
If you're still interested in writing an eval, we've noticed that these criteria make good evals. If you have any particular use case in mind for the model, can you come up with an eval that has some of these attributes?
- Multi-step reasoning
- Domain or Application specific
- Open-Ended responses
- Complex instructions
- The eval seems obvious but tricks the model in a novel way
Closing this PR, please open another PR with the provided suggestions.
If you want to create an eval with the same topic, then I would recommend asking the model to provide the chain of thoughts or its reasoning with the answer and using Includes or ModelGraded evaluation to evaluate the result. This way, the evaluation can test the model's capabilities in a better way.