Prompt from User
The user supplies text or another input to the interface.
19 learning checkpoints in the text-generation pipeline. Select a term in the navigation to jump to its explanation; each card links to the existing HAAW lessons that explore the idea in greater depth.
This is a teaching sequence, not a claim that every term is a distinct software component. In particular, “Translator” and “Embedded ID” are mnemonic labels explained in their cards.
← Full HAAW indexThe user supplies text or another input to the interface.
The tokenizer converts incoming text into pieces the model can process. “Translator” is a learning shorthand, not a separate language translator.
Each token is assigned an integer identifier from the model’s vocabulary.
The model looks up a learned numerical representation for each token ID.
Conceptual bridge: the token ID serves as the lookup key for an embedding. This is not normally a second, distinct ID.
The embedding vector represents a token numerically, with position information incorporated by the model architecture.
A stack of learned layers processes the vectors using attention and other transformations.
Tokens exchange context-dependent information, allowing the model to use relevant earlier tokens.
Within transformer layers, learned nonlinear transformations further process each token’s state.
The final layers produce context-sensitive numerical representations used to predict the next token.
The model projects its final state into a score for each possible next token.
The logits are transformed into a distribution over candidate tokens, subject to decoding settings.
A decoding rule chooses the next token, such as greedy selection or sampling.
The chosen next token is represented by its vocabulary ID and added to the sequence.
The tokenizer’s decoding side maps generated token IDs back into text fragments.
A decoded token fragment becomes part of the emerging response.
The model repeats next-token prediction until a stopping condition is reached.
The interface assembles or streams generated fragments into a readable answer.
The user sees the rendered answer in the application interface.