Update README.md
Browse files
README.md
CHANGED
|
@@ -83,15 +83,15 @@ directionally reliable, not as rigorously verified as the Swahili figures.
|
|
| 83 |
|
| 84 |
| Tokenizer | Vocab Size | Fertility | Entity Fragmentation |
|
| 85 |
|---|---|---|---|
|
| 86 |
-
| **otk-bpe sw-150k** | 150,000 | **1.210 (Best!)** | 0.341 |
|
| 87 |
| otk-bpe sw-100k | 100,000 | 1.233 | 0.435 |
|
|
|
|
| 88 |
| otk-bpe merged-150k | 150,000 | 1.264 | 0.519 |
|
| 89 |
| otk-bpe sw-50k | 50,000 | 1.285 | 0.626 |
|
| 90 |
| otk-bpe merged-100k | 100,000 | 1.302 | 0.672 |
|
| 91 |
-
|
|
| 92 |
| otk-bpe merged-50k | 50,000 | 1.393 | 0.822 |
|
| 93 |
| GPT-4o (o200k_base) | 200,019 | 1.841 | 0.768 |
|
| 94 |
-
| mBERT | ~119,547 | 2.071 | 0.575 |
|
| 95 |
| GPT-4 (cl100k_base) | 100,277 | 2.462 | 0.820 |
|
| 96 |
|
| 97 |
### Kinyarwanda
|
|
@@ -122,8 +122,8 @@ both metrics simultaneously.
|
|
| 122 |
| otk-bpe merged-100k | 100,000 | 1.409 | 0.502 |
|
| 123 |
| GPT-4o (o200k_base) | 200,019 | 1.478 | 0.479 |
|
| 124 |
| otk-bpe merged-50k | 50,000 | 1.486 | 0.620 |
|
| 125 |
-
| AfroXLMR | 250,002 | 1.597 |
|
| 126 |
-
| mBERT | ~119,547 | 1.616 | 0.388 |
|
| 127 |
| GPT-4 (cl100k_base) | 100,277 | 1.720 | 0.578 |
|
| 128 |
|
| 129 |
### English
|
|
@@ -146,18 +146,28 @@ additional languages in the same vocabulary.
|
|
| 146 |
|
| 147 |
### Reading the entity fragmentation numbers honestly
|
| 148 |
|
| 149 |
-
|
| 150 |
-
|
| 151 |
-
|
| 152 |
-
|
| 153 |
-
|
| 154 |
-
|
| 155 |
-
|
| 156 |
-
|
| 157 |
-
|
| 158 |
-
|
| 159 |
-
|
| 160 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 161 |
|
| 162 |
## How to Use
|
| 163 |
|
|
|
|
| 83 |
|
| 84 |
| Tokenizer | Vocab Size | Fertility | Entity Fragmentation |
|
| 85 |
|---|---|---|---|
|
| 86 |
+
| **otk-bpe sw-150k** | 150,000 | **1.210 (Best!)** | **0.341 (Best!)** |
|
| 87 |
| otk-bpe sw-100k | 100,000 | 1.233 | 0.435 |
|
| 88 |
+
| AfroXLMR | 250,002 | 1.597 | 0.441 |
|
| 89 |
| otk-bpe merged-150k | 150,000 | 1.264 | 0.519 |
|
| 90 |
| otk-bpe sw-50k | 50,000 | 1.285 | 0.626 |
|
| 91 |
| otk-bpe merged-100k | 100,000 | 1.302 | 0.672 |
|
| 92 |
+
| mBERT | ~119,547 | 2.071 | 0.575 |
|
| 93 |
| otk-bpe merged-50k | 50,000 | 1.393 | 0.822 |
|
| 94 |
| GPT-4o (o200k_base) | 200,019 | 1.841 | 0.768 |
|
|
|
|
| 95 |
| GPT-4 (cl100k_base) | 100,277 | 2.462 | 0.820 |
|
| 96 |
|
| 97 |
### Kinyarwanda
|
|
|
|
| 122 |
| otk-bpe merged-100k | 100,000 | 1.409 | 0.502 |
|
| 123 |
| GPT-4o (o200k_base) | 200,019 | 1.478 | 0.479 |
|
| 124 |
| otk-bpe merged-50k | 50,000 | 1.486 | 0.620 |
|
| 125 |
+
| AfroXLMR | 250,002 | 1.597 | 0.434 |
|
| 126 |
+
| mBERT | ~119,547 | 1.616 | **0.388 (Best!)** |
|
| 127 |
| GPT-4 (cl100k_base) | 100,277 | 1.720 | 0.578 |
|
| 128 |
|
| 129 |
### English
|
|
|
|
| 146 |
|
| 147 |
### Reading the entity fragmentation numbers honestly
|
| 148 |
|
| 149 |
+
At 150k vocab, OTK-BPE tokenizers win entity fragmentation **outright**, not
|
| 150 |
+
just fertility, for Swahili and Kinyarwanda — `sw-150k` and `kin-150k` both
|
| 151 |
+
have the lowest fragmentation rate of every tokenizer tested, dedicated or
|
| 152 |
+
general-purpose. The vocab-size increase from 50k to 150k didn't just narrow
|
| 153 |
+
the gap to larger multilingual tokenizers on this metric, it closed and then
|
| 154 |
+
reversed it for these two languages specifically.
|
| 155 |
+
|
| 156 |
+
The exceptions are French and English, where **mBERT** — not AfroXLMR — has
|
| 157 |
+
the best entity handling (0.388 and 0.285 respectively), edging out even the
|
| 158 |
+
merged tokenizer. This makes sense: mBERT's vocabulary, while smaller than
|
| 159 |
+
AfroXLMR's, was built with heavy exposure to major European-language
|
| 160 |
+
Wikipedia text including large volumes of proper nouns, and English/French
|
| 161 |
+
are exactly where that shows. The merged tokenizer's own English and French
|
| 162 |
+
entity handling (0.558 and 0.428) is competitive but not best-in-class for
|
| 163 |
+
those two languages specifically — a real, honest tradeoff of covering 4
|
| 164 |
+
languages in one shared vocabulary rather than dedicating full budget to
|
| 165 |
+
either.
|
| 166 |
+
|
| 167 |
+
**Net read**: don't assume general-purpose tokenizers automatically win on
|
| 168 |
+
entity handling just because they have larger vocabularies — that held at
|
| 169 |
+
the smaller 50k vocab size tested earlier in this project, but stopped
|
| 170 |
+
holding once vocab size reached 150k for the languages that needed it most.
|
| 171 |
|
| 172 |
## How to Use
|
| 173 |
|