Response to Reviewer tEGh
Thank you for reading our paper and for your constructive feedback! We have improved our paper based on your feedback.
With regard to the strengths:
* Re Interesting findings: For us, the most interesting result was that Claude 2 with long context did so well when given 100k tokens of the book. This is not something that we expected given recent work that is somewhat negative about long context LLMs (e.g. Lost in the Middle; Liu et al. 2023 -- https://arxiv.org/abs/2307.03172).
With regard to the weaknesses:
* We agree that we should have included a traditional machine translation method as a baseline. We have run baselines finetuned on the ~1100 available parallel sentences and included full details along with a table of results in the general response to all reviewers. We also agree that future work should explore other kinds of architectures/LLMs finetuned specifically for machine translation; we think an interesting research question is how to most effectively combine traditional massively multilingual machine translation data with instruction tuning/in-context learning capabilities. As you point out with the Robinson et al. paper, even though LLMs are trained on both kinds of data, the MT capabilities don’t always make it through.
* We agree that more interpretable evaluation is always better. Unfortunately analyzing the results in this way, especially across different kinds of retrieved context, is very time-consuming and error-prone since there is a lot of context retrieved for each example (as in Figures 7 and 8, let alone the 50K and 100K chunks). It also seems safe to say that we can’t automate this analysis using current LLMs, since they are the ones generating the outputs with errors. We think that the qualitative examples and analysis in the paper give a good sampling of the kinds of errors that the models and retrieval methods make, and the chrF scores match our subjective impressions of output quality well. The fact that the errors are qualitatively similar to hallucinations in LLMs more generally and that there are fewer errors with better LLMs—despite the exclusion from pretraining data—is evidence that in-context learning in LLMs is really improving and underscores the value of MTOB.
* We have conducted a comparison to low-resource MT and included the results in the response to all reviewers. But we will also clarify: we do not think that we claim in the paper that English <--> Kalamang translation is more difficult than translation with other low-resource languages. (Certainly, given equal amounts of data, we have no reason to think this would be the case.) Rather, we were trying to say the following:
a) We can be confident there isn’t a mass of in-domain training data hidden in the pretraining set, unlike languages with more speakers, so we can test data efficiency in a principled way. The fact that there are only ~1600 parallel sentences means that yes, it is probably harder from a traditional NMT perspective, but
b) We have the model learn from explanations in a grammar book to make the task easier, and
c) We show that the task is actually possible to a great extent using the human baseline.
So in some sense we are saying our task framing is actually easier than traditional low-resource MT from parallel sentences, because we have reason to believe that the task is possible.
With regard to the questions you asked:
1. Yes, we mention in the expanded Limitations section in the Appendix (page 22 under “Potential Contamination”) that the train/test parallel sentences are in a CSV file on GitHub as of February 2021, as part of the source code for Dictionaria. (And we mentioned in the introduction the steps we are taking to prevent additional contamination due to the release of this paper.) It is possible that LLMs were trained on it, or maybe it was filtered out because the CSV file is very messy. Regardless, we saw no signs that the model baseline outputs were memorized; they changed very reasonably with different kinds of provided context.
2. See the new baseline mentioned above that we ran in response to your feedback.
3. Thank you for the suggestion. We have re-evaluated all results using chrF++ and we will add the results to the paper; see the included numbers in the table in the general response to all reviewers. We find that the (relative) chrF results are very similar to chrF, with a slightly bigger gap between the model-based methods and the human baseline.