Skip to main content

Advancing Polish Language Modeling through Tokenizer Optimization in the Bielik v3 7B and 11B Series

AuthorsKrzysztof Ociepa et al.
Year2026
HF Upvotes6
arXiv2604.10799
PDFDownload
HF PageView on Hugging Face

Abstract

The development of the Bielik v3 PL series, encompassing both the 7B and 11B parameter variants, represents a significant milestone in the field of language-specific large language model (LLM) optimization. While general-purpose models often demonstrate impressive multilingual capabilities, they frequently suffer from a fundamental architectural inefficiency: the use of universal tokenizers. These tokenizers, typically designed to cover a broad spectrum of languages, often fail to capture the morphological nuances of specific languages like Polish, leading to higher fertility ratios, increased inference costs, and restricted effective context windows. This report details the transition from the universal Mistral-based tokenization to a dedicated Polish-optimized vocabulary for the Bielik v3 models, exploring the FOCUS-based embedding initialization, the multi-stage pretraining curriculum, and the subsequent post-training alignment involving Supervised Fine-Tuning, Direct Preference Optimization, and Reinforcement Learning through Group Relative Policy Optimization with verifiable rewards.


Engineering Breakdown

Plain English

This paper describes the development of Bielik v3 PL, a family of Polish-language large language models in 7B and 11B parameter sizes that addresses a critical inefficiency in general-purpose LLMs: their use of universal tokenizers that don't efficiently encode Polish morphology. The authors identified that universal tokenizers (like those in Mistral) produce higher token counts for Polish text, increasing inference costs and reducing effective context window size. Their core contribution is replacing the universal tokenizer with a Polish-optimized vocabulary that captures language-specific morphological patterns, resulting in lower fertility ratios and more efficient inference for Polish-language applications.

Core Technical Contribution

The primary innovation is a language-specific tokenization optimization that replaces universal tokenizer vocabularies with a carefully constructed Polish-optimized variant. Rather than accepting the token inefficiency inherent in covering 100+ languages simultaneously, the authors deliberately trade universality for specialization—creating a custom vocabulary that deeply understands Polish morphological patterns like grammatical cases, gender agreement, and verb conjugation. This approach demonstrates that for production systems targeting specific languages, accepting language-specialization allows dramatic improvements in tokenization efficiency metrics. The technical novelty lies not in a new tokenizer algorithm itself, but in the systematic analysis of morphological inefficiency and the empirical validation that custom vocabularies significantly outperform universal alternatives for language-specific deployment.

How It Works

The system begins with analysis of tokenization efficiency across the target language (Polish), measuring fertility ratios—the ratio of generated tokens to characters in input text. The authors take a base Mistral-7B and Mistral-11B architecture and replace the universal tokenizer (typically built on BPE or SentencePiece covering 32K-100K tokens) with a new vocabulary optimized for Polish linguistic patterns. The new tokenizer is trained on Polish language corpora to preferentially merge subword units that align with morphemes and common Polish word patterns, reducing the average tokens-per-character ratio. Once the tokenizer is rebuilt, the entire model undergoes continued training (or fine-tuning) on Polish data to adapt the embedding layer and all downstream parameters to work efficiently with the new vocabulary. At inference time, input text is tokenized using the Polish-optimized vocabulary, producing fewer tokens than the universal version, which reduces memory pressure, speeds up attention computation (quadratic in sequence length), and increases the practical context window.

Production Impact

For production teams building Polish-language systems, this approach directly reduces inference latency and cost: fewer tokens mean fewer forward passes through the model layers, lower GPU/TPU memory usage during inference, and longer effective context windows without architectural changes. A 20-30% reduction in token count (typical for language-specific optimization) translates to proportional speedups in decoding time and reduced per-request inference cost, making real-time applications like chatbots or search-ranking more economically viable. However, adoption requires committing to Polish-language specialization—the model and tokenizer become language-specific assets, so multilingual pipelines need separate models, complicating deployment infrastructure. Teams must also revalue their existing universal-tokenizer-based datasets and cached embeddings, as they become incompatible with the new vocabulary. The trade-off is favorable for high-volume, single-language production systems but creates organizational friction for platforms serving multiple languages.

Limitations and When Not to Use This

The paper's scope is inherently limited to Polish and does not demonstrate generalizability across language families—Slavic, Romance, Germanic, and tonal languages have dramatically different morphological structures, so results may not transfer to other language-specific optimizations. The approach assumes substantial in-language training data is available and that model developers can afford the cost of retraining embeddings and continued training on new vocabularies; resource-constrained teams may lack the compute budget to realize benefits. The paper does not address how cross-lingual transfer or multilingual fine-tuning would be affected by language-specific tokenizers, limiting applicability in scenarios requiring some degree of language interoperability. Additionally, there is no discussion of how tokenizer changes affect downstream tasks like translation, code-switching, or proper noun handling—morphological optimization may inadvertently harm performance on inputs that deviate from standard Polish text.

Research Context

This work builds directly on decades of tokenizer research (BPE, SentencePiece, WordPiece) and extends recent findings that universal tokenizers are a bottleneck in multilingual LLM efficiency. The Bielik series itself is part of the broader European initiative to develop high-quality language-specific foundation models (similar to French's Mistral-based models and German efforts), recognizing that English-centric model development underserves non-English-speaking populations. The paper contributes empirical evidence supporting the hypothesis that language specialization is a viable efficiency strategy, opening research directions into whether selective multilingualism (e.g., tokenizers optimized for 3-5 languages rather than 100+) offers better efficiency-generality trade-offs. This work also reinforces the importance of vocabulary design as a first-class optimization target, not merely a preprocessing detail, influencing how future multilingual models might partition their tokenization strategies.


:::tip Subscribe Get weekly breakdowns of papers like this in AI Letters - the newsletter for engineers building production AI systems. :::


Back to Research Lab → · Subscribe to AI Letters →

© 2026 EngineersOfAI. All rights reserved.