Summary
This paper sets out to create a large language model specifically designed for translation and translation-related tasks. This is done by continual pre-training of LLaMA-2 on monolingual and parallel data in multiple languages, then instruction-tuning on a curated and filtered labeled dataset of translation-related tasks (translation, post-editing, named entity recognition).
The resulting model, TowerInstruct, achieves impressive results on translation, named entity recognition, automatic post-editing, and grammatical error correction (with GEC being a held-out task unseen during instruction-tuning), performing on par with much larger models. Furthermore, the authors publicly release the model, dataset, and evaluations.
This is an important contribution that will be of interest to the industry. My main quibble is that I wish that the set of translation tasks explored were more extensive (e.g. including different domains or modalities).
Reasons to accept
1. The approach to training a translation-focused LLM is useful. Furthermore, it is effective, as shown by several extensive evaluations.
2. In addition to the paper, the authors will release their LLM, dataset, and evaluation framework. This will foster future research in the area.
3. The analysis in section 4 is interesting and clearly shows the impact of each component of the training "recipe".
Reasons to reject
1. I am a bit perplexed by the choice of "translation-related" tasks in the paper: translation, automatic post-editing, named entity recognition, and grammatical error correction. I don't think named entity recognition or grammatical error correction are specifically translation-related (although they may be useful for translation, like several other tasks), while more related tasks are omitted (e.g., metric development, quality estimation, parallel data curation, bilingual lexicon induction). In addition, I think it would be useful to see more comprehensive coverage of machine translation -- including subtasks like domain-specific MT, low-resource or dialectal translation, or multimodal MT.
2. In some cases, it is unclear how experimental settings are selected. Examples: L100 "We train for 4 epochs using a low learning rate and a large batch size", L121 "We prompt TOWER and closed models in a 0-shot fashion and others with 5 examples randomly selected from the development set." It would be good to know how these design decisions were made (optimization on a development set?).
Questions to authors
1. Not a question, but a suggestion: "automatic post-edition" should be "automatic post-editing" (in a couple of places).
2. Why did you select those 10 languages? (EN, DE, FR, NL, IT, ES, PT, KO, RU, ZH)
3. L63: Why do you need language identification?