← Latest papers
🤖 machine learning

Building Better Activation Oracles

This paper enhances Activation Oracles (AOs) by introducing four training improvements to address hallucinations and vagueness while releasing AObench, the first comprehensive evaluation suite, to advance scalable, end-to-end interpretability.

Original authors: Jan Bauer, Celeste De Schamphelaere, Adam Karvonen, Niclas Luick, Neel Nanda

Published 2026-06-03
📖 5 min read🧠 Deep dive

Original authors: Jan Bauer, Celeste De Schamphelaere, Adam Karvonen, Niclas Luick, Neel Nanda

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 have a super-smart robot (a Large Language Model) that writes stories, solves math problems, or answers questions. But inside its "brain," there are billions of tiny electrical signals firing in a language no human can understand. These signals are called activations.

For a long time, we've wanted to peek inside that brain to see why the robot made a certain decision. Enter the Activation Oracle (AO). Think of an AO as a "translator" or a "biographer" for the robot. You show the translator the robot's electrical signals, ask, "What were you thinking right here?" and the translator tries to explain it in plain English.

However, the original translators had some big problems:

  1. They were vague: Instead of saying "I was thinking about the word 'apple'," they would say, "I was thinking about the concept of the sentence." (Not very helpful!)
  2. They hallucinated: They would make up details that weren't actually in the signals.
  3. They were "cheaters": Sometimes, they didn't actually read the signals at all. They just looked at the words before and after the signal and guessed the answer based on those words. This is called "text inversion."

The authors of this paper wanted to build a better translator. They didn't just tweak the code; they rebuilt the training process in four specific ways. Here is how they did it, using some everyday analogies:

1. The Better Textbook (The Conversational Dataset)

The Problem: The old translator was trained on a textbook (called LatentQA) that asked tricky questions about complex prompts. The answers were often impossible to find just by looking at the signals, so the translator just started guessing or giving vague answers.
The Fix: The authors created a new textbook. They took the robot's own "thought process" (its internal reasoning), cut it in half, and asked a different AI to write a question about the second half that could only be answered by looking at the signals of the first half.
The Analogy: Imagine teaching a student to read a map. The old method gave them a map and asked, "Where is the treasure?" without showing them the map's legend. The new method shows them a specific landmark on the map and asks, "What is the terrain like right here?" This forces the translator to actually look at the signals, not just guess based on context.
Result: This was the biggest improvement. The new translator became much more specific and stopped being so vague.

2. Looking at More Layers (The Multi-Layer Feed)

The Problem: The old translator only looked at one specific "floor" of the robot's brain (around layer 25% or 50% deep). But the robot's "thoughts" are spread out across many floors.
The Fix: The authors realized that the most interesting "thoughts" happen around the 60-80% mark. So, instead of looking at just one floor, they fed the translator signals from five consecutive floors at once.
The Analogy: If you are trying to understand a movie, watching just one frame (one layer) tells you very little. Watching a short clip of five frames (five layers) gives you the motion and context you need to understand what's happening.
Result: This helped the translator understand the "movie" of the robot's thinking better, especially when comparing different models.

3. Training on "Live" Data (On-Policy Rollouts)

The Problem: The old translator was trained on old, static data (like a library of books written before the robot existed). It was like teaching a driver using a map of a city that hasn't changed in 50 years.
The Fix: They started training the translator on data generated by the robot while it was actually thinking.
The Analogy: Instead of teaching a translator using a script from a play that ended years ago, they put the translator in the audience while the play is happening live. This ensures the translator learns how the robot thinks right now, not how it thought in the past.
Result: This helped a little bit, but it wasn't the magic bullet. It made the translator slightly better at understanding the robot's current state.

4. Turning Up the Volume (Injection Strength)

The Problem: When showing the signals to the translator, the "volume" (or strength) of the signal was a bit too quiet. The translator was trying to hear a whisper in a noisy room.
The Fix: They turned up the "volume" of the signals they fed into the translator.
The Analogy: Imagine trying to listen to a friend in a loud concert. If you just hand them a note, they might miss it. If you shout the note (increase the strength), they are much more likely to hear it correctly.
Result: This didn't change the overall score much, but it significantly reduced hallucinations. The translator was less likely to make things up because the real signal was louder and clearer.

The Final Result: AObench

To prove their new translator was better, the authors built a new test called AObench. Think of this as a "driver's license test" specifically for these translators. It checks:

  • Vagueness: Does the translator give a concrete answer or a fluffy one?
  • Hallucination: Does the translator make up facts?

The Verdict:
By combining all four fixes, the new translator is much better than the old one.

  • It is less vague (it gives specific answers).
  • It hallucinates less (it tells the truth more often).
  • It follows instructions better.

The authors admit that while the translator is still not perfect, they have laid a solid foundation. They have shown that if you give the translator better training data, show it more of the brain's activity, and turn up the volume, it becomes a much more reliable window into how AI models think.

In short: They took a translator that was guessing and being vague, and turned it into a translator that is actually listening, looking at the whole picture, and telling the truth.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →