Descriptive Collision in Sparse Autoencoder Auto-Interpretability: When One Explanation Describes Many Features
This paper identifies and formalizes "descriptive collision," a previously overlooked failure mode in sparse autoencoder interpretability where distinct features share identical natural-language explanations, and proposes new metrics to penalize such non-discriminatory annotations that artificially inflate reported interpretability.
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 massive library with millions of unique books (these are the "features" inside a smart computer program). To make sense of this library, you hire a team of librarians to write a short, one-sentence summary for every single book.
The goal is that if you read the summary, you should be able to find that exact book and no other.
However, this paper discovers a major problem with how these summaries are currently written. The author calls this "Descriptive Collision."
Here is the breakdown of the problem and the proposed solution, using simple analogies:
1. The Problem: Too Many Books, Too Few Labels
Imagine you have 1,000 different books in your library. The librarians are asked to write a short label for each one.
- The Reality: Instead of writing 1,000 unique descriptions, the librarians keep reusing the same few phrases.
- The Example: The phrase "Plural Nouns" is used as the label for 101 different books.
- The Result: If you see a book labeled "Plural Nouns," you have no idea which of the 101 specific books you are actually looking at. It's like having 101 different people in a room all wearing the exact same name tag that says "John." If you call out "John," all 101 people turn around. You haven't identified a specific person; you've just identified a group.
The paper analyzed a real dataset of 722 features and found that 82% of them share their label with at least one other feature. In fact, the most common label ("plural nouns") was shared by 101 distinct features across different parts of the computer model.
2. Why Current Tests Miss This
Currently, researchers test if a label is "good" by asking: "Does this label accurately describe what happens when the feature turns on?"
- The Flaw: The paper argues this test is blind to the collision problem.
- The Analogy: Imagine you are testing if the name tag "John" is a good description for a specific person. You ask, "Does this person respond to the name John?" The answer is "Yes." So, the test says the label is perfect.
- The Reality: The test doesn't ask, "Does only this person respond to the name John?" Because 100 other people also respond to "John," the label fails to identify the specific individual, even though it is technically "true" for everyone.
The paper proves mathematically that as long as a label describes the feature correctly, current scoring systems will give it a high score, even if that label is shared by dozens of other features.
3. The Proposed Solution: The "Distinguisher" Test
The author suggests we need a new way to grade these labels. Instead of just asking, "Is this label true?" we should ask, "Can this label tell this feature apart from its neighbors?"
They propose two new methods:
Discrimination Scoring: This is like a "spot the difference" game. You take a feature and its label, and you compare it to a "neighbor" feature that is very similar.
- The Test: "Here is a sentence. Does the label 'Plural Nouns' tell us if Feature A is active, or if Feature B (which is also about nouns) is active?"
- The Goal: A good label should be able to say, "This sentence activates Feature A, but not Feature B." If the label is just a generic "Plural Nouns" that fits both, it gets a low score because it fails to distinguish them.
Collision-Adjusted Detection: This is a simpler, cheaper fix. It takes the current score and divides it by how many other features share that label.
- The Math: If a label is shared by 100 features, its "goodness" score gets divided by 100. A label shared by 1 feature keeps its full score. This punishes generic labels that are too broad.
4. Why This Happens (The Root Cause)
The paper uses Goodhart's Law to explain this. This law says: "When a measure becomes a target, it ceases to be a good measure."
- The Trap: Researchers are trying to get high scores on "detection" (does the label predict the feature?).
- The Result: The system (or the AI writing the labels) learns that the easiest way to get a high score is to use broad, safe, generic phrases like "plural nouns" or "he" that are true for many things.
- The Space Problem: There are millions of features (the "input space"), but only a limited number of short, simple English phrases (the "description space"). You simply cannot give a unique, short name to millions of things without running out of words and reusing them.
Summary
The paper claims that current methods for explaining AI features are overconfident. They tell us a label is "accurate" when it is actually just vague.
- Old Way: "This label is 95% accurate!" (Because it describes the feature correctly).
- New Way: "This label is 95% accurate, but it is shared by 100 other features, so it only identifies this specific feature 1% of the time."
The author concludes that we need to stop just checking if a label is true, and start checking if a label is unique enough to find the specific feature among millions of others.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.