Position Problem › Absolute vs. Relative Position

Michael BrenndoerferUpdated June 5, 20256 min read
Language AI HandbookAll chapters
Part 14 of 67Positional Encoding
Chapter 96Position Problem › Absolute vs. Relative Position
Reading section 6 of 11 · Absolute vs. Relative Position · 6 minSection 6 of 11 · 6 min

Book contents

Section 6 of 11 · 6 min read

Position Problem › Absolute vs. Relative PositionOne section · Sections in this chapter6 / 11 ↓
Reading tools Definitions & inline links

Choose your expertise level to adjust how many terms are explained. Beginners see more tooltips, experts see fewer to maintain reading flow. Hover over underlined terms for instant definitions.

Article links

Make inline references clickable

A final conceptual distinction shapes the entire design space for positional representations: should we encode where each token is in absolute terms, or should we encode how tokens relate to each other in relative terms? This choice is not merely technical; it reflects a hypothesis about what kinds of positional patterns matter most for language.

Absolute positional encoding assigns each position a fixed vector. Position 0 always gets the same encoding, position 1 always gets the same encoding, and so on, regardless of the sequence. The attention mechanism receives absolute location signals and must learn to compute relative positional information by comparing absolute positions.

Relative positional encoding directly encodes the distance or relationship between pairs of positions. Instead of saying "this token is at position 5," relative encoding says "this token is 3 positions before the query token." The attention mechanism directly incorporates these relative distances, without needing to infer them from absolute locations.

Out[13]:
Visualization
Diagram showing five word boxes labeled The cat sat on mat with position indices 0 through 4.
Absolute position assigns a fixed index to each token regardless of context. The numbers 0 through 4 label where each word appears in the sequence. Any downstream computation that needs to know token distances must derive that information by comparing absolute indices.
Diagram showing relative distances from the query token sat to other tokens, with arrows and signed integer labels.
Relative position encodes the signed distance from a chosen query token (here 'sat' at position 2). Tokens to the left have negative offsets, tokens to the right have positive offsets. This representation directly supports distance-based reasoning without requiring absolute index comparison.

Each approach has significant trade-offs. Absolute encoding is simpler to implement: just add a position vector to each token embedding before feeding it to the model. The attention mechanism then sees combined content-position vectors and can, with sufficient capacity, learn to extract relative positional information by computing differences between absolute positions. The original Transformer and later models such as BERT and GPT all use absolute positional encoding.

The limitation of absolute encoding is that it requires the model to learn the mapping from absolute to relative positions implicitly. If the model sees "position 3 attends to position 1" during training, it must generalize to "position 103 attends to position 101" at inference. These are the same relative offset (+2) expressed as different absolute positions. With enough data and capacity, models can learn this generalization, but it is not guaranteed, and it may require more training examples than relative encoding.

Relative encoding directly captures these distance-based relationships. Instead of embedding absolute positions, the model embeds the distances i−ji - j between query position ii and key position jj. This representation is translation-invariant by construction: a distance of +2 means the same thing regardless of whether we are at positions 1 and 3 or positions 101 and 103. The model does not need to generalize across absolute positions.

The drawback of relative encoding is architectural complexity. Absolute positional vectors can be added to token embeddings once at the input layer, and the rest of the model is unchanged. Relative positions depend on pairs of positions, not individual positions, so they cannot simply be added to the input. The attention score between positions ii and jj must explicitly incorporate information about the distance i−ji - j. This requires modifying the attention computation itself, rather than changing only the input preprocessing. The result is a more expressive model that is also harder to implement efficiently.

Modern architectures increasingly favor relative or hybrid approaches. RoPE (Rotary Position Embedding) cleverly encodes relative positions through rotation operations that integrate naturally with the standard attention dot product. ALiBi (Attention with Linear Biases) adds a simple learned bias to attention scores based on distance, achieving relative encoding with minimal architectural change. We will explore both approaches in dedicated chapters.

Why Relative Positions Are Linguistically Natural

The preference for relative encoding in recent architectures reflects a linguistic observation about local relationships. Most syntactic and semantic relationships in language are local and relative, not global and absolute. A subject typically appears within a few words of its verb, and this proximity holds whether the subject-verb pair appears at the beginning of a sentence or in the middle of a long document. A determiner ("the," "a") always immediately precedes the noun phrase it introduces, and this is a relative relationship independent of absolute position. Anaphoric pronouns refer back to noun phrases that appeared somewhere earlier in the discourse, a backward-pointing relative relationship.

If positional representations encode relative distances well, the model can more easily learn these universal syntactic generalizations. If they encode only absolute positions, the model must learn to apply each generalization at every possible absolute location, multiplying the number of patterns it needs to internalize.

This does not mean absolute encoding is useless. Document-level reasoning, reference tracking across very long spans, and certain ordering tasks may benefit from knowing absolute position. A model that knows it is processing the first sentence of a document versus the twentieth sentence might behave differently. Hybrid approaches that encode both absolute and relative information are an active area of research.