Factual Retrieval in LLMs Is a Redundant, Distributed and Non-Contiguous Process
This paper reveals that factual retrieval in large language models relies on redundant, distributed, and non-contiguous computational paths across multiple layers, challenging the assumption of localized knowledge storage and explaining the mismatch observed in knowledge editing.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine a Large Language Model (LLM) as a massive, multi-story library where every book contains a tiny piece of the world's knowledge. For a long time, researchers thought that if you wanted to find a specific fact—like "What is Angela Merkel's mother tongue?"—the answer was stored in one specific room (a specific layer of the model) and retrieved in a straight line, floor by floor.
This paper argues that reality is much more chaotic, flexible, and redundant. Here is the breakdown of their findings using simple analogies:
1. The "Non-Contiguous" Elevator Ride
The Old Idea: To get an answer, the model's internal "elevator" (the data processing) stops at every single floor, checking the information at each step, from the ground floor to the top.
The Paper's Discovery: The elevator doesn't stop at every floor. In fact, it often skips floors entirely.
- The Analogy: Imagine you are trying to get a package delivered. You don't need the delivery truck to stop at every single house on the street. Sometimes, the truck can jump from the 2nd floor directly to the 8th floor, ignoring the floors in between, and still get the package to the right door.
- The Finding: The authors found that to retrieve a fact, the model only needs a specific, scattered set of layers. It can "teleport" the information through the network, skipping many intermediate steps that turn out to be unnecessary for that specific fact.
2. The "Redundant Backup Routes"
The Old Idea: There is one "correct" path to find a fact. If you block that path, the model fails.
The Paper's Discovery: The model has multiple backup routes that work just as well.
- The Analogy: Think of a city with a main highway. If you block the highway, traffic doesn't stop; it instantly reroutes to a complex network of backroads, side streets, and even a different highway that takes a longer, more winding route. Both routes get you to the same destination, but they look completely different.
- The Finding: For almost every fact they tested, the researchers found a "primary path" (the shortest, most efficient route) and at least one "alternative path" (a longer, deeper route). If you block the primary path, the model can still find the answer using the backup path. This means the knowledge isn't stored in just one place; it's distributed and redundant.
3. The "Minimal Team" vs. The Whole Orchestra
The Old Idea: The whole model works together to generate every answer.
The Paper's Discovery: You only need a small, specific team of layers to do the job.
- The Analogy: Imagine a symphony orchestra playing a song. You might assume every musician is needed for every note. But the authors found that for a specific fact, only a few specific musicians (layers) are actually playing the notes. The rest of the orchestra is essentially silent or doing something else.
- The Finding: They identified a "minimal attribute computation path." This is the smallest group of layers required to produce the correct answer. Surprisingly, this group often ends in the middle of the model. Once the information is processed by these few layers, the rest of the model doesn't need to do any more heavy lifting to know the answer.
4. The "Editing Mismatch" Mystery
The Old Idea: If you want to change a fact in the model (e.g., change "Merkel's language is German" to "French"), you should edit the specific layer where that fact is stored.
The Paper's Discovery: Where the fact is "stored" and where you need to "edit" it are often in different places.
- The Analogy: Imagine a factory assembly line. The part that makes the product might be at the beginning of the line, but the part that fixes a mistake might be at the very end. If you try to fix the product at the beginning, you might break the machine.
- The Finding: Because the model uses these scattered, redundant paths, simply finding the layer where the data "looks" like the answer isn't enough. To successfully edit a fact, you often have to intervene at a specific "transformation stage" in the path, not necessarily where the knowledge seems to be sitting.
Summary of the "Big Picture"
The authors conclude that the way LLMs store and retrieve facts is not like a filing cabinet where you pull a single drawer. Instead, it's like a highly flexible, redundant neural network where:
- Knowledge is distributed: It's spread across many layers, not locked in one.
- Paths are flexible: The model can take short, direct routes or long, winding backup routes to find the same answer.
- Skips are normal: The model often ignores layers in between, jumping straight to where the information is needed.
This explains why AI models are so robust (they have backups) but also why it's so hard to pinpoint exactly "where" a fact lives or how to reliably change it. The process is a complex, multi-step dance that happens in a non-linear, scattered way.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.