[KongchangAI]
Concept

WordPiece

A subword tokenization algorithm that determines symbol merges by maximizing language model likelihood. It serves as the core tokenization method adopted by models such as BERT, producing a vocabulary of subword units that balances coverage and compactness.

Core Facts

Timeline (last 90 days)

Oct 16

In a warm English encoding with bert-base-uncased, Normalization consumed 88% of the encoding time, while WordPiece accounted for only 8%.

Unverified50%
Oct 14

BAAI/bge-small-en-v1.5 uses a WordPiece tokenizer, which splits snake_case and camelCase into meaningless fragments.

Unverified50%
Oct 13

The WordPiece tokenizer's ## prefix marks the latter part of a subword; for example, gatito is split into ga, ##ti, ##to, and gato also contains ##to, causing shared tokens between the query and the document and producing false similarity.

Unverified50%
Oct 11

A Tokenizer is responsible for splitting raw text into token sequences that the model can process; mainstream approaches include BPE, WordPiece, and SentencePiece.

Unverified50%
Sep 30

The choice among the three tokenization algorithms involves different trade-offs among vocabulary size, rare-word coverage, and cross-lingual generalization ability.

Unverified50%
Sep 30

WordPiece was proposed by Google and adopted by BERT; its merge criterion maximizes the likelihood of a language model rather than purely counting frequencies.

Unverified50%
Sep 16

Mainstream subword tokenizers (such as BPE and WordPiece) treat different written forms of the same word (e.g., hello, Hello, HELLO, Héllo) as independent, mutually unrelated vocabulary entries.

Unverified50%
Sep 16

Fixed vocabulary sizes typically range from 30,000 to 100,000 entries.

Unverified50%
Sep 16

WordPiece determines its merging strategy with the objective of maximizing language model likelihood.

Unverified50%

All Facts (10)

Verified

Modern LLMs generally use BPE (Byte Pair Encoding) or WordPiece algorithms for tokenization.

80%
Unverified

In a warm English encoding with bert-base-uncased, Normalization consumed 88% of the encoding time, while WordPiece accounted for only 8%.

50%
Unverified

BAAI/bge-small-en-v1.5 uses a WordPiece tokenizer, which splits snake_case and camelCase into meaningless fragments.

50%
Unverified

The WordPiece tokenizer's ## prefix marks the latter part of a subword; for example, gatito is split into ga, ##ti, ##to, and gato also contains ##to, causing shared tokens between the query and the document and producing false similarity.

50%
Unverified

A Tokenizer is responsible for splitting raw text into token sequences that the model can process; mainstream approaches include BPE, WordPiece, and SentencePiece.

50%
Unverified

WordPiece was proposed by Google and adopted by BERT; its merge criterion maximizes the likelihood of a language model rather than purely counting frequencies.

50%
Unverified

The choice among the three tokenization algorithms involves different trade-offs among vocabulary size, rare-word coverage, and cross-lingual generalization ability.

50%
Unverified

Mainstream subword tokenizers (such as BPE and WordPiece) treat different written forms of the same word (e.g., hello, Hello, HELLO, Héllo) as independent, mutually unrelated vocabulary entries.

50%
Unverified

Fixed vocabulary sizes typically range from 30,000 to 100,000 entries.

50%
Unverified

WordPiece determines its merging strategy with the objective of maximizing language model likelihood.

50%

Source Articles