Summary
This paper is about using a separate tokenizer per language under the multilingual scenario.
Since the tokenizer most current LLMs are depending on, i.e. splitting a word into subwords based on their frequencies, is highly biased toward frequent languages, it may harm the performance for low-resource languages.
This work suggests training a tokenizer for each language; which the authors coin "trans-tokenization."
One challenge that the trans-tokenization approach should overcome is adapting the token embeddings pre-trained from specific (usually frequent) languages into low-resource one, since for low-resource languages there hardly exist enough data to obtain high-quality token embeddings.
The authors try to address the challenge through the use of parallel corpora.
Using off-the-shelf statistical machine translation (SMT) tool, it finds the mappings between word (or token) in one language and another language.
Based on the frequencies of mappings for a specific word or token, a token embedding for a low-resource language is obtained via weighted-summing the source token embeddings.
For the evaluation, Tatar language is mainly used as a low-resource language while adopting Mistral as a base LLM.
The evaluation is done on language modeling, language understanding, text summarization, and machine translation.
For baselines, a model without tuning (w/ original tokenizer; Mistral) and with fine-tuning (w/ original tokenizer; MistralFT, w/ language-specific tokenizer + random initialization; MistralRAND, and w/ language-specific tokenizer + initializing embeddings for tokens in both languages with the original ones; MistralBASE) are used.
The proposed model, TweetyMistral, is a model with fine-tuning, where embeddings are initialized based on trans-tokenization.
On low-resource evaluations, the TweetyMistral models generally brought performance gain.
From language modeling experiments, the TweetMistral models whose embeddings and the first and last two layers are fine-tuned performed the best, while MistralFT slightly underperformed TweetMistral ones.
In language understanding, text summarization, and machine translation experiments, the authors tested an interesting baseline: using off-the-shelf translation applications like Google Translate and Microsoft Translator.
Though in text summarization and machine translation the performance of using translation applications performed the best.
The authors also evaluated whether the trans-tokenization approach can also improve mid-resource languages.
In language modeling experiments with Dutch language, the proposed algorithm performed the best, even with much fewer training tokens and even compared to GPT-Neo model trained on Dutch with the same tokenizer.
In language understanding experiments with Dutch, the trans-tokenization approach outperformed other models on 1-shot and 2-shot setups while on 0-shot setup the original Mistral performed the best.
Overall, the paper is well-organized and accompanies a wide coverage of experiments.
Configurations of each experiment are presented in detail in appendices, which will help replicating the work.
Though some questions about the improvements remain, I believe this work will give insights to those who want to transfer a model trained on frequent languages into other languages.
Questions to authors
1. How is the performance of mid-resource language understanding, summarization, or translation, especially when compared to Mistral+GTrans? In my opinion part of the reason that TweetyMistral underperforms low-resource language understanding is due to its extremely low similarity to English, which may lead to incorrect mappings via SMT.
2. In summarization evaluation, Mistral Instruct is used in making texts longer; did it add any important context about summarization, by using what it already knows, which may change the true answer for the summarization task?
3. Google Translate is already used in generating short summarization data. Could it affect the performance of short text translation evaluation scores, like the data contamination appeared in social media section?
Typo: SQAD → SQuAD