CoRect: Context-Aware Logit Contrast for Hidden State Rectification to Resolve Knowledge Conflicts
CoRect addresses knowledge conflicts in Retrieval-Augmented Generation by identifying and rectifying layers where parametric priors suppress retrieved context through a label-free, logit-contrast-based hidden state rectification method.
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 you are a student taking a history exam. You have a textbook open in front of you (this is the "Retrieved Evidence"), but you also have a very strong memory of what you learned in a different class years ago (this is the "Parametric Knowledge").
Suddenly, the textbook says the war ended in 1980, but your brain is screaming, "No! It was 1979!" Even though you see the correct answer right in front of you, your brain "overwrites" the truth with your old memory. You end up writing 1979 on the test. This is exactly what happens to Large Language Models (like ChatGPT) in a process called RAG (Retrieval-Augmented Generation). They get the right info, but their "internal bias" wins the argument.
The researchers created a tool called CoRect to fix this. Here is how it works using three simple analogies:
1. The "Internal Saboteur" (The Problem)
The researchers discovered that the mistake doesn't happen at the very end when the model is "speaking." Instead, it happens deep inside the model's "brain" (the hidden layers).
Think of the model like a factory assembly line. In the early stages, the workers are correctly picking up the right parts (the correct facts). But as the product moves toward the end, a "saboteur" worker in the middle of the line (a specific layer in the neural network) swaps the correct part for a wrong one because they are so used to doing it the old way. This is what they call Parametric Suppression.
2. The "Smart Detective" (Stage 1: Token Selection)
Before fixing the problem, the model needs to know what the correct answer should be, without being told.
Imagine a detective walking into a crime scene. Instead of just guessing, the detective looks at two things:
- The Clues: What does the evidence (the context) suggest?
- The Witnesses: Is the model's own "attention" actually looking at the evidence?
CoRect uses a "Detective" phase to find a Target Token. It compares the model's thoughts with the evidence versus its thoughts without the evidence. If a specific word (like "1980") gets a huge boost when the evidence is present, the detective marks it as the "True Target."
3. The "Volume Knob" (Stage 2: Hidden State Rectification)
Now that the detective has found the truth, how do we stop the "saboteur" in the factory?
Most old methods tried to "shout" the right answer at the very end of the assembly line. This is like a manager yelling at the finished product to change its color—it's messy and often ruins the product's quality.
CoRect does something much more elegant. It goes back to the specific "saboteur" worker in the middle of the line and simply turns down their volume.
If the saboteur is trying to push "1979" into the stream, CoRect applies a mathematical "counter-force" to cancel out that specific wrong signal. It doesn't force the model to say "1980"; it simply removes the interference that was preventing "1980" from coming through. It’s like noise-canceling headphones for the model's brain—it silences the "internal noise" so the "truthful signal" can be heard clearly.
The Result
By "cleaning" the internal thoughts rather than just forcing the final words, the model stays smart and fluent. It doesn't start talking like a robot; it just stops lying to itself. It becomes a student who actually listens to the textbook instead of just relying on a faulty memory.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.