Papers › Separating Tongue from Thought: Activation Patching Reveals Language-Agnostic Concept...

Separating Tongue from Thought: Activation Patching Reveals Language-Agnostic Concept Representations in Transformers

13 Nov 2024arXiv:2411.08745archive 2025-07-28

Clément Dumas, Chris Wendler, Veniamin Veselovsky, Giovanni Monea, Robert West

A central question in multilingual language modeling is whether large language models (LLMs) develop a universal concept representation, disentangled from specific languages. In this paper, we address this question by analyzing latent representations (latents) during a word translation task in transformer-based LLMs. We strategically extract latents from a source translation prompt and insert them into the forward pass on a target translation prompt. By doing so, we find that the output language is encoded in the latent at an earlier layer than the concept to be translated. Building on this insight, we conduct two key experiments. First, we demonstrate that we can change the concept without changing the language and vice versa through activation patching alone. Second, we show that patching with the mean over latents across different languages does not impair and instead improves the models' performance in translating the concept. Our results provide evidence for the existence of language-agnostic concept representations within the investigated models.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 10 code samples harvested from 1 repository linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 5 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 5 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 10 samples from 1 repository, 6 ran (1 with no instrument failure; 5 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

butanium/llm-lang-agnostic officialmentioned in papermentioned on GitHubpytorchSyntology: 10 samples, 6 ran (5 instrument-failed) · 4 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

10 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 5 where Syntology's instrument failed) · 4 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

5ran · our draft was wrong
1ran
4unverified

Licence: 10 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from butanium/llm-lang-agnostic. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

butanium/llm-lang-agnostic official repository 10 samples, 6 ran (5 instrument-failed) · 4 unverified
add_spaces in 5 papers src/prompt_tools.py ran · our draft was wrong no licence file found · pointer only · d9985dd3f6df938f · report fixture: signature tokens:list/1/str · returned list · level recorded 2026-09-25
byte_string_to_list src/prompt_tools.py ran · our draft was wrong fingerprinted no licence file found · pointer only · f0cedcf96dce07ce · report fixture: signature input_string:str/0/str · returned list · level recorded 2026-09-25
k_subplots src/display_utils.py ran · our draft was wrong no licence file found · pointer only · 4a5f917729414302 · report fixture: signature k:int/0/int, size:tuple/1/int · returned tuple · level recorded 2026-09-25
repeat_prompt src/interventions.py ran no licence file found · pointer only · db389b8baf11d2e3 · report fixture: signature nn_model:callable/0/?, words:list/1/str, rel:str/0/str, sep:str/0/str, placeholder:str/0/str · returned TargetPrompt · level recorded 2026-09-25
token_prefixes src/prompt_tools.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 516d409723a7793f · report fixture: signature token_str:str/0/str · returned list · level recorded 2026-09-25
ulist src/utils.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 59c98f4117e2ce93 · report fixture: signature lst:list/1/int · returned list · level recorded 2026-09-25
get_cloze_dataset src/load_dataset.py unverified no licence file found · pointer only · d3d8b54b3ae77dd9 · report
get_word_translation_dataset src/load_dataset.py unverified no licence file found · pointer only · 01d5c8d8d8623cf6 · report
load_cloze src/load_dataset.py unverified no licence file found · pointer only · 407ca7792a91113c · report
plot_ci_plus_heatmap src/display_utils.py unverified no licence file found · pointer only · fa631efa3ef9c566 · report

Tasks

Language ModelingLanguage ModellingTranslationWord Translation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Patching

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections