Before you can trust that idea, you need to own a handful of symbols and pictures the parent note throws at you. This page builds each one from nothing, in an order where each rests on the one before it.
Every symbol on this page is ultimately about tokens, so we start here.
The fixed list of all possible tokens is called the vocabulary.
Look at the figure: the sentence gets chopped into boxes (tokens), and each box points to its ID number in the vocabulary list on the right. That arrow — text → list of IDs — is the very first thing that happens to any input.
Now that a token is defined, two whole sequences of them appear constantly in the parent note.
Notice n and m can differ — the answer is usually a different length from the question. That is exactly why T5 is text-to-text: both the question and the answer are just sequences of tokens.
The parent note writes p(yt∣y<t,x). That little y<t is a compact and crucial idea.
The figure shows the decoder writing token by token. The red box is the token being written right now (yt); the black boxes to its left are y<t, the history it is allowed to look at. It may never peek at boxes to its right — those aren't written yet.
Multiplying many tiny probabilities gives a vanishingly small number that computers handle badly. Enter the log.
The figure shows the curve of logp for p between 0 and 1. Notice: when p is close to 1 (confident and correct), logp is near 0. When p is tiny (the model was almost sure it was something else), logp plunges toward −∞. So −logp is small when you're right and huge when you're wrong — a perfect "surprise / penalty" meter.
The parent says T5 is an encoder–decoder. Here is what those words picture.
In the figure the left block (encoder) has arrows going both ways between input tokens — it reads bidirectionally. The right block (decoder) has arrows only pointing forward, and the red arrows are cross-attention: the bridge letting the output look at the input.
I can say what a token and the vocabulary V are ::: A token is one small text chunk (word/subword); V is the finite set of all tokens the model can read or write.
I can read x=(x1,…,xn) and y=(y1,…,ym) ::: x is the input token sequence of length n; y is the target token sequence of length m; the two lengths may differ.
I know what y<t means ::: All target tokens before position t, i.e. (y1,…,yt−1) — the output written so far.
I can read the bar ∣ ::: p(A∣B) = probability of A given that B holds; it means "the answer depends on this context."
I know why the chain rule uses ∏ ::: The joint probability of a sequence factorizes exactly into a product of per-token conditional probabilities.
I know why log appears ::: It turns the product of tiny probabilities into an additive, numerically stable sum.
I know why the loss has a minus sign ::: logp is negative for p<1; the minus makes the penalty positive, small when correct, huge when wrong.
I can write the cross-entropy loss ::: L=−∑t=1mlogp(yt∣y<t,x).
I can distinguish encoder, decoder, cross-attention ::: Encoder reads input bidirectionally; decoder writes output left-to-right; cross-attention lets each output token consult the encoder's reading.
I know what a task prefix and a sentinel token are ::: A prefix is the instruction glued to the front of the input; a sentinel is a special labelled blank token marking a corrupted span.