Contents Arithmetic, counting and letters

Why it gets things wrong

Arithmetic, counting and letters

The familiar explanation for why a chatbot miscounts letters is that it never sees letters, only chunks. That is true about the input, but it weakly explains the counting failures: the one benchmark built to test it found tokenization properties only weakly predicted counting correctness, while word length and true character count predicted it more strongly.

A tokenizer breaks text into subword chunks: the word annoyingly might split into annoying and ly, or into other chunks depending on the vocabulary,1 and the GPT-2 tokenizer splits the word numbers into n and umbers, a break that says nothing about spelling.9 Character-level splitting would avoid this, but sequences get much longer and performance suffers, so chunks are the deliberate trade.1 A 2025 paper adds a second reason: written text almost never spells words out, since spelling is self-evident to a reader, so the training signal for a word's letters is nearly absent.2

CharBench's 2026 measurements evaluated character tasks over 175,000 strings sampled from MiniPile across the seven models it tested, GPT-4o among them.3 Average accuracy was 77.34 percent on counting how often a letter occurs and 47.96 percent on counting distinct characters. Its finding about causes matters more: tokenization correlated only weakly with counting correctness, while word length and true count mattered more. For positional questions the story flips: longer tokens do obscure where a character sits.3 A 2026 study of three open model families agrees: character counts were recoverable from internal layers at above 80 percent probe accuracy in most layers, while stated answers sat near a 33 percent random baseline, attenuated by later-layer components.4

Task Result What predicted it
Count a letter's occurrences 77.34 percent average, 89.45 for GPT-4o word length, true count
Count distinct characters 47.96 percent average, 65.51 for GPT-4o word length, true count
Name a character's position worse with longer tokens token length

Arithmetic has its own version: the RoBERTa tokenizer encodes 520 as one chunk while 521 splits into two, and that inconsistency can undermine reliable alignment of digits by place value.5 A 2023 study reports GPT-4 at 4.3 percent on multi-digit multiplication.6 Separately, a 2026 study defines an arithmetic load and places the point where predicted multiplication accuracy falls to half at about 68.6 for GPT-5.4 and about 52.9 for GPT-4o.7 Earlier work concludes that these tasks are handled by linearised subgraph matching rather than systematic reasoning, with performance declining rapidly as task complexity increases.8

None of this is one story. Chunking explains position errors and barely explains counting errors, the figures belong to the named models on their stated dates, and nothing here says the ceiling is fixed.

References

Quizzes
  1. The benchmark built to test the tokenization explanation of counting errors reported which result?

    • Word length mattered more than token splits
    • Token splits were by far the strongest predictor of a wrong count
    • Splits mattered only for the largest models

    Tokenization properties correlated only weakly with counting correctness, while the queried word's length and its true character count carried more of it.

  2. Longer chunks are measured support for errors about a character's ____ inside a word.

    • position
    • identity
    • frequency

    The same benchmark found longer tokens strongly predict positional errors, while tokenization properties were only weakly correlated with counting correctness.

  3. A character count can often be read out of the model's internal layers even when the answer it gives is wrong.

    • True
    • False

    Probes recovered counts above 80 percent in most layers while stated answers sat near a third, with later-layer components attenuating the correct signal.

Comments

No comments yet. Start the conversation.