179 questions
No questions match those filters.
You need to adapt an English-centric LLM's tokenizer to...
This is one of the questions in the full AI/ML interview bank. Pro unlocks all 1789 questions; Premium includes the same bank plus the highest daily Practice limit.
See plansBPE learns subword units by statistically merging frequently co- occurring character pairs, which works well for concatenative languages like English precisely because the root stays intact as a contiguous block while prefixes and suffixes attach around it — “play” stays “play” whether it’s “playing” or “played.” Retraining that same algorithm on Arabic or Hebrew text and expecting equivalent behavior misunderstands the morphology it’s operating on.
Semitic languages build words around a root-and-pattern system: a three-consonant root (say k-t-b, related to “writing”) gets interleaved with vowels and templatic patterns to produce “kitab” (book), “kutub” (books), “kataba” (he wrote) — the root doesn’t sit at one edge, it’s woven through the entire word, changing shape with every inflection. Run BPE over this and each conjugated form gets segmented into different, unrelated token sequences, so the model has no shared representation connecting “kitab” and “kutub” the way it would connect “play” and “playing” — it has to independently learn every surface form of every root as if they were unrelated words.
The fix is to stop optimizing purely for subword frequency statistics and instead respect the morphology directly: run a morphological analyzer as a preprocessing step that decomposes each word into its root and its templatic pattern before tokenization, or use a character- aware encoder (a character-CNN or dedicated character-level model) that can learn to recognize a persistent root pattern across surface variations rather than treating each inflected form as tokenically unrelated to the others.