Papers › Identifying Knowledge Editing Types in Large Language Models

Identifying Knowledge Editing Types in Large Language Models

29 Sep 2024arXiv:2409.19663archive 2025-07-28

Xiaopeng Li, Shangwen Wang, Shezheng Song, Bin Ji, Huijun Liu, Shasha Li, Jun Ma, Jie Yu

Knowledge editing has emerged as an efficient technology for updating the knowledge of large language models (LLMs), attracting increasing attention in recent years. However, there is a lack of effective measures to prevent the malicious misuse of this technology, which could lead to harmful edits in LLMs. These malicious modifications could cause LLMs to generate toxic content, misleading users into inappropriate actions. In front of this risk, we introduce a new task, Knowledge Editing Type Identification (KETI), aimed at identifying different types of edits in LLMs, thereby providing timely alerts to users when encountering illicit edits. As part of this task, we propose KETIBench, which includes five types of harmful edits covering most popular toxic types, as well as one benign factual edit. We develop four classical classification models and three BERT-based models as baseline identifiers for both open-source and closed-source LLMs. Our experimental results, across 42 trials involving two models and three knowledge editing methods, demonstrate that all seven baseline identifiers achieve decent identification performance, highlighting the feasibility of identifying malicious edits in LLMs. Additional analyses reveal that the performance of the identifiers is independent of the reliability of the knowledge editing methods and exhibits cross-domain generalization, enabling the identification of edits from unknown sources. All data and code are available in https://github.com/xpq-tech/KETI. Warning: This paper contains examples of toxic text.

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

By repository: official repository: 9 samples from 1 repository, 7 ran (5 with no instrument failure; 2 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 between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

xpq-tech/keti officialmentioned in papermentioned on GitHubpytorchMITSyntology: 9 samples, 7 ran (2 instrument-failed) · 2 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

9 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 2 where Syntology's instrument failed) · 2 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.

2ran · our draft was wrong
5ran
2unverified

Licence: 1 of the 9 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from xpq-tech/keti. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

xpq-tech/keti official repository 9 samples, 7 ran (2 instrument-failed) · 2 unverified
evaluate_model in 54 papers abalation_closellm.py ran MIT (permissive) · 91a84b1a09f3183e · report fixture: signature model:callable/0/?, dataloader:DataLoader/0/? · returned tuple · level recorded 2026-09-24
evaluate_model in 54 papers close_source_llms_main.py ran MIT (permissive) · 611b5daad6c596b7 · report fixture: signature model:callable/0/?, dataloader:list/1/dict · returned tuple · level recorded 2026-09-24
hierarchical_subsequence in 47 papers easyeditor/util/nethook.py ran MIT (permissive) · 920b394e7ad80c53 · report fixture: signature sequential:callable/0/?, first:NoneType/0/?, last:NoneType/0/?, after:NoneType/0/?, upto:NoneType/0/?, share_weights:bool/0/bool, depth:int/0/int · returned Sequential · level recorded 2026-09-24
preprocess in 284 papers
census: 11 implementations from 13 papers, 10 distinct outputs across 5 buckets, one shared input per bucket
abalation_closellm.py ran MIT (permissive) · f85a4563ca4ff777 · report fixture: signature tokens_log_probs:list/1/list, edited_llm_tokenizer:MockTokenizer/0/?, token_num:int/0/int · returned tuple · level recorded 2026-09-24
preprocess in 284 papers
census: 11 implementations from 13 papers, 10 distinct outputs across 5 buckets, one shared input per bucket
close_source_llms_main.py ran MIT (permissive) · 5bd374a013b0e83b · report fixture: signature tokens_log_probs:list/1/list, edited_llm_tokenizer:MockTokenizer/0/? · returned tuple · level recorded 2026-09-24
recursive_copy in 51 papers easyeditor/util/nethook.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 70f6ab8bde55420e · report fixture: signature x:dict/0/?, clone:bool/0/bool, detach:bool/0/bool, retain_grad:bool/0/bool · returned dict · level recorded 2026-09-22
subsequence in 51 papers easyeditor/util/nethook.py ran · our draft was wrong MIT (permissive) · 440ff98c2b1ae1aa · report fixture: signature sequential:callable/0/?, first_layer:NoneType/0/?, last_layer:NoneType/0/?, after_layer:NoneType/0/?, upto_layer:NoneType/0/?, single_layer:NoneType/0/?, share_weights:bool/0/bool · returned Sequential · level recorded 2026-09-24
get_features in 57 papers extract_features.py unverified MIT (permissive) · 96c1f23ed670da04 · report
get_features_all_hs extract_features.py unverified MIT (permissive) · 03ab176ee52a77ac · report

Tasks

Domain Generalizationknowledge editing

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

AttentionSoftmax

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