Language Model Tokenizers Introduce Unfairness Between Languages

Aleksandar Petrov, Emanuele La Malfa, Philip H. S. Torr, Adel Bibi
5/17/2023
cs.CLcs.LG

No official code found. Best implementation: AleksandarPetrov/tokenization-fairness (6 stars, MIT, last commit 2023-11-28).

Abstract

Recent language models have shown impressive multilingual performance, even when not explicitly trained for it. Despite this, there are concerns about the quality of their outputs across different languages. In this paper, we show how disparity in the treatment of different languages arises at the tokenization stage, well before a model is even invoked. The same text translated into different languages can have drastically different tokenization lengths, with differences up to 15 times in some cases. These disparities persist even for tokenizers that are intentionally trained for multilingual support. Character-level and byte-level models also exhibit over 4 times the difference in the encoding length for some language pairs. This induces unfair treatment for some language communities in regard to the cost of accessing commercial language services, the processing time and latency, as well as the amount of content that can be provided as context to the models. Therefore, we make the case that we should train future language models using multilingually fair subword tokenizers.

View on arXivView PDF

Code Implementations(1)

MIT
63HTML, PythonApr 29, 20232 years agoMIT

Cite this paper

@article{petrov2023language,
  title  = {Language Model Tokenizers Introduce Unfairness Between Languages},
  author = {Aleksandar Petrov and Emanuele La Malfa and Philip H. S. Torr and Adel Bibi},
  year   = {2023},
  eprint = {2305.15425},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2305.15425v2},
  journal = {NEURIPS 2023 2023}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2305.15425.svg)](https://codeofpaper.com/paper/2305.15425)

Discussion