Data-driven Circuit Discovery for Interpretability of Language Models
This paper critiques existing hypothesis-driven circuit discovery methods for producing dataset-specific circuits that fail to capture the true mechanistic diversity of language models, and proposes Data-driven Circuit Discovery (DCD), a new framework that clusters examples by processing similarity to reveal multiple distinct, high-fidelity circuits for a single task.
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 giant, super-smart robot (a Language Model) that can write stories, do math, and solve puzzles. Scientists want to understand how this robot thinks. They call this "Mechanistic Interpretability."
The traditional way scientists have tried to do this is like trying to find the "engine" of a car by looking at a single, specific trip. They say, "Okay, the robot just drove from Point A to Point B. Let's map out exactly which gears turned to make that happen." They call this mapped-out path a Circuit.
The Problem: The "One-Size-Fits-All" Trap
The paper argues that the old way of doing this is flawed because it makes two bad guesses:
- The Dataset Guess: It assumes the specific examples the scientists used (like a specific sentence structure) represent all ways the robot can do the task.
- The Single-Engine Guess: It assumes the robot uses just one specific set of gears (circuit) to solve the task, no matter how the question is asked.
The Discovery: The Robot Has Many Engines
The researchers tested this by giving the robot the same task but with slight variations (like changing the names in a story, or writing the math problem in words instead of numbers).
They found that:
- When they mapped the robot's "engine" for a story with names like "John and Mary," it looked completely different from the engine used for a story with names like "Person X and Person Y."
- Even worse, if they mixed two totally different tasks (like "find the object" and "do math") into one big pile of data, the old method still tried to force a single map onto it. It created a messy, confusing circuit that was a "Frankenstein" mix of both tasks, rather than realizing the robot was actually switching between two different engines depending on the input.
The Solution: Data-Driven Circuit Discovery (DCD)
To fix this, the authors propose a new method called Data-Driven Circuit Discovery (DCD).
Think of it like this:
- Old Method: You ask a group of people to solve a puzzle. You look at everyone's solution and try to draw one master blueprint that explains how everyone solved it. If some people used a hammer and others used a screwdriver, your blueprint becomes a confusing mess of both tools.
- New Method (DCD): You first look at the people and group them by how they are solving the problem. You put all the "hammer-users" in one room and all the "screwdriver-users" in another. Then, you draw a separate, clean blueprint for the hammer group and a different, clean blueprint for the screwdriver group.
How DCD Works (The Metaphor)
- Sort the Data: Instead of forcing the robot to use one path, DCD looks at every single example the robot processes. It asks, "Does this example make the robot's internal gears spin in a similar way to that other example?"
- Create Groups: It sorts the examples into "clusters" based on how the robot handles them.
- Find Specific Circuits: It then finds a specific, clean "engine map" for each group.
The Results
When they used this new method:
- They found that the robot actually uses multiple distinct mechanisms (engines) for what humans think is just "one task."
- The new maps (circuits) were much more accurate (faithful) and simpler (sparser) than the old messy maps.
- Crucially, the robot's internal organization didn't care about human labels like "Math" or "Story." It organized itself by the structure of the input. DCD respects the robot's internal logic rather than forcing human categories onto it.
In Summary
The paper says: "Stop trying to find one universal engine for a task. The robot is smarter and more flexible than that. It has different engines for different situations. Our new method, DCD, lets the data tell us where the boundaries are, so we can find the right engine for the right job, rather than forcing a single, confused engine map onto everything."
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.