OpenLID-v3: Improving the Precision of Closely Related Language Identification -- An Experience Report
This paper presents OpenLID-v3, an enhanced language identification system that improves precision for closely related languages and noise detection through expanded training data, merged language clusters, and a dedicated noise label, while also highlighting the trade-off between precision and coverage in ensemble approaches.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are running a massive library that collects books from every corner of the internet. Your goal is to sort these books onto the correct shelves based on the language they are written in. This task is called Language Identification (LID).
However, the internet is messy. It's full of short, confusing snippets, typos, code, and languages that sound almost identical to each other. Existing tools (like OpenLID and GlotLID) are like librarians who are good at sorting obvious books (like English or Spanish) but often get confused when two languages are "cousins" (like Bosnian and Croatian) or when a page is just gibberish.
This paper is an experience report from a team at the University of Oslo who built a new, upgraded librarian called OpenLID-v3. Here is how they improved the system, explained simply:
1. The Problem: The "Trash Bin" and the "Confusing Cousins"
The previous version of their librarian (OpenLID-v2) had three main headaches:
- The Trash Bin: If the librarian saw something that wasn't a real language (like computer code or broken text), it didn't have a "Not a Language" shelf. Instead, it forced the item onto a random language shelf, often piling up garbage on a specific shelf (like Ligurian) just because it was the only one left with room.
- The Missing Script: For Serbian, the librarian only knew the Cyrillic alphabet. If someone wrote Serbian using Latin letters (which is very common), the librarian thought it was actually Croatian or Bosnian.
- The Cousins: Languages that are very similar (like the Scandinavian languages or the Romance languages of Northern Italy) were often mixed up because the librarian wasn't trained enough to hear the tiny differences.
2. The Solution: OpenLID-v3
The team fixed these issues by giving the librarian a better training manual and a new set of rules:
- Adding a "Garbage" Shelf: They created a special label called "not-a-language" (zxx_Zxxx). Now, when the librarian sees code or gibberish, it can put it in the trash bin instead of mislabeling it as a real language.
- Learning New Scripts: They added training data for Serbian written in the Latin alphabet, so the librarian can finally tell the difference between Serbian and its cousins.
- Merging the Confusing Groups: For languages that are so similar they are practically the same (like certain Arabic dialects or Persian varieties), the librarian now treats them as one big "Macrolanguage" group rather than trying to force a distinction that doesn't exist in the data.
- The "Double-Check" Team: They tried a strategy where two librarians (OpenLID-v3 and GlotLID) look at the same book. If they both agree on the language, the team accepts it. This "ensemble" approach made the sorting incredibly precise, though it meant they had to throw away some books they weren't 100% sure about.
3. The Test Drive
The team didn't just guess; they tested OpenLID-v3 against the old versions and the competitor (GlotLID) using three types of test drives:
- The Clean Test: Using standard, perfect sentences (like the Universal Declaration of Human Rights). Here, everyone performed well.
- The "Cousin" Test: They created special tests for tricky groups:
- Bosnian/Croatian/Serbian: They found that while the new model was better, these languages are still hard to tell apart, especially on social media where people mix grammar and slang.
- Italian/French Romance: They discovered that some "Occitan" texts were actually "Francoprovençal," and the old tools kept mislabeling them as Ligurian. The new tools handled this better but still struggled with the nuances.
- Scandinavian: They found that Norwegian (Bokmål and Nynorsk) and Danish/Swedish are very easily confused. The new model was better at spotting the differences, but the "Double-Check" team was the most accurate.
4. The Big Takeaway
The paper concludes that OpenLID-v3 is a solid upgrade, especially for handling messy web data and distinguishing between very similar languages.
- Precision vs. Coverage: The "Double-Check" team (Ensemble) was the most precise (fewest mistakes), but it was also the most cautious. It refused to guess on low-resource languages, meaning it covered fewer languages overall.
- The "Trash" Problem: The ability to label "not-a-language" is a huge win, preventing garbage from contaminating the language shelves.
- The Reality of the Web: The authors note that standard tests (like FLORES+) are too clean. Real web data is messy, short, and often valid in multiple languages at once. To truly fix this, we need more training data that reflects this messy reality, not just perfect sentences.
In short, OpenLID-v3 is a smarter, more cautious librarian that knows when to say "I don't know" or "This isn't a language," making the final collection of books much cleaner, even if it takes a little longer to sort them.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.