Finding

Sign in with GitHub
← Publications

Finding · P74 · Author-curated

APT4's tokenization contributes to arithmetic accuracy differences between Bielik-PL-11B-v3.0-Instruct and Bielik-11B-v3.0-Instruct through its handling of the no-break space, not through digit segmentation.

Published by @stw2 · 2026-09-14 · Sources, measurements and interpretation are supplied by the author.

Structured assertion

Relation: Contributes through a channel

factor
Digit and punctuation tokenization policyTokenizer property concerned.
subject tokenizer
APT4 tokenizerTokenizer whose handling contributes.
comparator tokenizer
Mistral-derived tokenizerTokenizer compared with.
outcome
arithmetic accuracy differences between Bielik-PL-11B-v3.0-Instruct and Bielik-11B-v3.0-InstructOutcome contributed to.
channel
the no-break space (U+00A0) as thousands separatorChannel of the contribution.
excluded channel
digit segmentationChannel without a contribution.

Experimental provenance

Method and evaluation protocol
Decision rule of the plan for the digit-tokenization mechanism: refutes if digit segmentation is identical on bare and comma-grouped numerals and no tokenizer-attributable format-differential deficit exists in GSM8K's format domain; partial if digit segmentation is identical but a separator-level tokenizer-attributable deficit exists; confirms only if segmentation differs on bare or comma-grouped numerals.
Dataset
2,500 synthetic arithmetic items generated with seed 20260703, each in four number formats and two instruction languages.Version: unspecified · Access: public
Reported results
Tokens per number equal in 5 of 6 renderings, differing only with no-break-space grouping; no-break-space differential 0.1736 [0.1535, 0.1956]; comma-against-space interaction -0.0035 [-0.023, 0.0136]; 14 of 1,319 GSM8K test final answers contain a comma and 0 a space or no-break space. Outcome of the rule: partial.
Uncertainty and replication
Rests on the intervals of the contributing findings.
Limitations
The conditions of the refutes branch are also met as written; partial applies because a separator-level deficit exists, and the original report gave refutes. GSM8K final answers do not use the no-break space. The two models differ by 20B tokens of continued pretraining and by post-training as well as by the tokenizer; answer-only probes do not measure chain-of-thought arithmetic; MLX bf16 numerics differ from the paper's evaluation stack.

Paper citations

arXiv:2604.10799v1 →Revision supplied by author
  1. Table 6, p. 12, GSM8K column; Section 3, p. 3

Concept definitions

Reuse the defining version and key when the meaning fits your assertion.

Contributes through a channel

The factor of the subject tokenizer, against the comparator tokenizer, contributes to the outcome through channel and not through excluded_channel.

Key contributes_through · version b0f7daf6-d1ff-4a89-a255-3c00464a3b96

Mistral-derived tokenizer

Tokenizer of the original Bielik v3 models, derived from Mistral's.

Key mistral_tokenizer · version bd3d8329-e626-4805-9fff-f83f146769a7

Digit and punctuation tokenization policy

How a tokenizer segments digits, punctuation and special characters.

Key digit_tokenization_policy · version 85dfefb0-eb84-4deb-b93c-7b494a10b283

APT4 tokenizer

Polish-optimised tokenizer of the Bielik v3 PL models.

Key apt4 · version d497f94d-5373-4652-887c-55c001b6472c

Exact references

derived from

2f04e3ac-4c60-437e-93d3-0e5644c55b44

APT4 splits digits one token per digit.

derived from

ab426953-7fb7-4a21-9c58-78317771084a

Digit segmentation is identical outside no-break-space grouping.

derived from

db752f7a-f88d-47e4-910d-67d6dbadd5fb

No format-differential deficit between comma and space grouping.

derived from

73e6d8ab-194e-4a4a-ae68-c1cb3586ca61

The separator-level tokenizer-attributable deficit.

derived from

2dbc96aa-9e0d-4ec0-97da-5cbab3338222

GSM8K's exposure to the separator channel.

related

36da68d9-97cf-4575-ad42-ed56e0e895e9

GSM8K final answers contain no no-break spaces, so this channel does not reach the reported GSM8K difference.

related

1832c8a3-4857-4668-b703-73fdb0289e46

Bears on the GSM8K difference that disputes this claim.