Single features under the microscope

Averaged scores across thousands of features can only say so much. At some point a paper has to zoom into a handful of individual ones and show, in detail, what a monosemantic feature actually looks like from the inside.

This theme follows two such case studies read from both directions, what makes each feature fire and what removing it does to the model's output, including one traced back further still, through the chain of upstream features that cause it to activate in the first place.

Cunningham et al. (2023) cash out the sparse autoencoder's promise not in aggregate scores but in a handful of individual dictionary features, examined from both ends. Reading from the input side, the apostrophe feature (feature 556) is shown to fire almost exclusively on apostrophe tokens, distinguishing it from the polysemantic residual-stream dimension that shares its top activations. Reading from the output side, ablating that feature selectively suppresses the logit for the following "s" token, the effect a monosemantic apostrophe detector should have on possessives and contractions like "let's". The closing-parenthesis feature, a layer-5 unit whose unembedding directly predicts closing-parenthesis tokens, extends the method into automatic feature-circuit detection, which ablates each upstream feature and ranks it by how much the ablation lowers the target's activation, tracing which earlier features -- detecting dates, acronyms, and other parenthesis-preceding phrases -- cause it to fire. Together the two case-study features make monosemanticity a demonstrated property, not just a scored one.