Papers › The Impact of Prompts on Zero-Shot Detection of AI-Generated Text

The Impact of Prompts on Zero-Shot Detection of AI-Generated Text

29 Mar 2024arXiv:2403.20127archive 2025-07-28

Kaito Taguchi, Yujie Gu, Kouichi Sakurai

In recent years, there have been significant advancements in the development of Large Language Models (LLMs). While their practical applications are now widespread, their potential for misuse, such as generating fake news and committing plagiarism, has posed significant concerns. To address this issue, detectors have been developed to evaluate whether a given text is human-generated or AI-generated. Among others, zero-shot detectors stand out as effective approaches that do not require additional training data and are often likelihood-based. In chat-based applications, users commonly input prompts and utilize the AI-generated texts. However, zero-shot detectors typically analyze these texts in isolation, neglecting the impact of the original prompts. It is conceivable that this approach may lead to a discrepancy in likelihood assessments between the text generation phase and the detection phase. So far, there remains an unverified gap concerning how the presence or absence of prompts impacts detection accuracy for zero-shot detectors. In this paper, we introduce an evaluative framework to empirically analyze the impact of prompts on the detection accuracy of AI-generated text. We assess various zero-shot detectors using both white-box detection, which leverages the prompt, and black-box detection, which operates without prompt information. Our experiments reveal the significant influence of prompts on detection accuracy. Remarkably, compared with black-box detection without prompts, the white-box methods using prompts demonstrate an increase in AUC of at least 0.1 across all zero-shot detectors tested. Code is available: https://github.com/kaito25atugich/Detector.

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: 8 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 5 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 3 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 9 samples from 1 repository, 8 ran (3 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 between 2026-09-24 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

kaito25atugich/detector officialmentioned in paperpytorchSyntology: 9 samples, 8 ran (5 instrument-failed) · 1 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: 8 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 5 where Syntology's instrument failed) · 1 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
3ran; the contract check could not run
3ran
1unverified

Licence: 9 of the 9 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 kaito25atugich/detector. “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.

kaito25atugich/detector official repository 9 samples, 8 ran (5 instrument-failed) · 1 unverified
find_max_index utils.py ran fingerprinted no licence file found · pointer only · d3ccb79d5f676d7a · report fixture: signature target_list:list/1/float, threshold:float/0/float · returned int · level recorded 2026-09-24
get_precision_recall_metrics utils.py ran; the contract check could not run (RAISES) no licence file found · pointer only · 1952adc5b5b7b860 · report fixture: signature true_labels:ndarray/1/int, scores:ndarray/1/float · returned tuple · level recorded 2026-09-24
get_prompt in 99 papers tmp/generate_estimation_prompts.py ran fingerprinted no licence file found · pointer only · 9a9e58cbb8b7370b · report fixture: signature system_prompt:str/0/str, batch:str/0/str, model_name:str/0/str · returned str · level recorded 2026-09-24
get_roc_metrics utils.py ran; the contract check could not run (RAISES) no licence file found · pointer only · 4480f9be0b362363 · report fixture: signature true_labels:ndarray/1/int, scores:ndarray/1/float · returned tuple · level recorded 2026-09-24
perplexity in 22 papers detector.py ran no licence file found · pointer only · 318a521cfba1fbf1 · report fixture: signature encoding:BatchEncoding/0/?, logits:Tensor/3/float, median:bool/0/bool, temperature:float/0/float, prompt_len:int/0/int · returned ndarray · level recorded 2026-09-24
preprocess_string detector.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 1ebc2d66bc8ec407 · report fixture: signature sss:str/0/str · returned str · level recorded 2026-09-24
prim_tree in 5 papers detector.py ran; the contract check could not run (RAISES) no licence file found · pointer only · 595d1d025c7e692d · report fixture: signature adj_matrix:ndarray/2/float, alpha:float/0/float · returned float · level recorded 2026-09-26
remove_special_tokens in 10 papers tmp/paraphraser.py ran · our draft was wrong fingerprinted no licence file found · pointer only · f6d96afa1d60eb61 · report fixture: signature text:str/0/str, is_return:bool/0/bool · returned str · level recorded 2026-09-24
get_paraphraser tmp/paraphraser.py unverified no licence file found · pointer only · ebcdce09885239f8 · report

Tasks

Text Generation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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