← Latest papers
💬 NLP

Morphology Aware Reversible Semantic Tokenization and Hierarchical Word Composition for Tamil Language Models

This paper proposes a morphology-aware, reversible semantic tokenization system with hierarchical word composition for Tamil that outperforms existing baselines in translation quality while significantly reducing sequence length and inference costs under a fixed model budget.

Original authors: Anand Murugan

Published 2026-08-04
📖 4 min read☕ Coffee break read

Original authors: Anand Murugan

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 trying to teach a robot to speak a new language. To do this, you have to break the language down into tiny building blocks that the robot can understand. In the world of computer science, this is called "tokenization." Think of it like a chef chopping ingredients: a standard chef might chop everything into tiny, uniform cubes (like "subword" tokens), which is fast and works for almost any recipe. But for a complex dish like a traditional Tamil curry, chopping everything into identical cubes might destroy the delicate layers of flavor. Tamil is a language where a single word can be a whole sentence packed with meaning—telling you who did what, when, and how. If you chop that word apart without understanding its grammar, you lose the recipe.

This paper explores a different way to chop the ingredients. Instead of just cutting words into random pieces, the researcher built a system that understands the "grammar anatomy" of Tamil words before they are fed to the robot. They ask: Can we teach the robot the exact rules of how Tamil words are built (like a stem plus a tense plus a case marker) so it understands the meaning better? And if we do give it all that extra detail, can we still make the robot fast enough to be useful, or does it get bogged down by too much information?

The researcher, Anand Murugan, tackled this by creating a special "Morphology-Aware" system for Tamil. They started by building a massive digital library of Tamil word rules using 12 different "Finite-State Transducers" (think of these as super-precise, rule-following robots that can break a word down into its parts, like a stem, a tense, and a number). They tested two main ways to feed this information to a translation model (a computer program that translates Tamil to English).

The first method, called "morphology-flat," was like laying out every single ingredient on the table separately. If a word meant "by the tree," the system didn't just say "tree"; it said "tree" + "noun" + "plural" + "by." This gave the model a huge amount of detail. The result? It was the best at translating. In a strict test of 3,539 sentences, it achieved a score of 10.63 (BLEU), beating other popular systems by a noticeable margin. It was the most accurate, but it was also "verbose," meaning it had to process a lot more tokens (building blocks) for every single word, which makes the computer work harder.

The second method, called the "word-composer," was a clever compromise. It tried to keep the best of both worlds. It kept the main "stem" of the word (the lemma) visible, but it bundled all the tiny grammar details (like tense and case) into a single "summary" token. Then, just before the model finished its translation, it would peek back at the original detailed notes to make sure it got the specifics right. This approach was much more efficient. It reduced the number of steps the computer had to take by about 59.3% (dropping from an average of 71.48 steps per sentence down to 29.08). While it was slightly less accurate than the "flat" method on very long, formal sentences, it still beat all the other external systems tested and was much faster to run.

The paper explicitly rules out a few ideas that might seem obvious. For instance, they tried putting the "peek back" step earlier in the process, but that didn't work; the model needed to see the whole sentence context first before looking up the grammar details. They also tried splitting the grammar summary into two parts, but that just added extra work without improving the translation. The author is careful to note that while their system works great for small models with limited data, they haven't proven yet if this advantage holds true for massive, super-powerful AI models that have seen the entire internet.

In the end, the study shows that for Tamil, understanding the "anatomy" of words helps the computer translate better than just guessing the chunks. However, you don't have to lay every single bone on the table to get a good result; a smart summary that knows where to look for the details works almost as well, but with much less effort. It's a reminder that sometimes, giving a machine a little bit of human-like grammar knowledge can make it a much better translator, especially when it's learning a complex language like Tamil.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →