DPIC: Decoupling Prompt and Intrinsic Characteristics for LLM Generated Text Detection

Large language models (LLMs) have the potential to generate texts that pose risks of misuse, such as plagiarism, planting fake reviews on e-commerce platforms, or creating inflammatory false tweets. Consequently, detecting whether a text is generated by LLMs has become increasingly important. Existing high-quality detection methods usually require access to the interior of the model to extract the intrinsic characteristics. However, since we do not have access to the interior of the black-box model, we must resort to surrogate models, which impacts detection quality. In order to achieve high-quality detection of black-box models, we would like to extract deep intrinsic characteristics of the black-box model generated texts. We view the generation process as a coupled process of prompt and intrinsic characteristics of the generative model. Based on this insight, we propose to decouple prompt and intrinsic characteristics (DPIC) for LLM-generated text detection method. Specifically, given a candidate text, DPIC employs an auxiliary LLM to reconstruct the prompt corresponding to the candidate text, then uses the prompt to regenerate text by the auxiliary LLM, which makes the candidate text and the regenerated text align with their prompts, respectively. Then, the similarity between the candidate text and the regenerated text is used as a detection feature, thus eliminating the prompt in the detection process, which allows the detector to focus on the intrinsic characteristics of the generative model. Compared to the baselines, DPIC has achieved an average improvement of 6.76\% and 2.91\% in detecting texts from different domains generated by GPT4 and Claude3, respectively.

Paper

References (48)

Scroll for more · 36 remaining

Similar papers

Peer review

Reviewer eWrN7/10 · confidence 4/52024-06-19

Summary

In this paper, the authors present DPIC, a novel model for detecting LLM-generated text, which centers on having an auxiliary LLM reverse-generate prompt on candidate text, and then letting the LLM re-generate the answers to the prompt and classify them based on the similarity between the candidate and the re-generated text. The authors experimented it with competitors on multiple datasets and claimed that they achieved better performance.

Strengths

- This paper is well written and detailed. - The experiments for the model were adequate. - The core idea of the model is easy to understand and interesting.

Weaknesses

- Lack of detail in evaluation metrics. - The testing model is underrepresented. - Details of the model's consumption of computational resources are missing.

Questions

1. In the manuscript, I did not find out any details about the AUROC evaluation metrics used, such as its formula, or the evaluation steps. I understand that this is a commonly used evaluation metric, but an academic paper should be complete and detailed. The authors only briefly indicated its mathematical meaning, which I think is not sufficient. 2. For the testing part of the models, the authors used three representative commercial closed-source models: gpt-3.5, gpt-4, and claude3 to generate text for specific prompts for model testing. While it can be argued that closed-source models are more difficult to access than open-source models to infer that it is more challenging to recognize text generated by closed-source models, this inference is from the perspective of detection model builder, and applied to a real-world scenario, even if the candidate text is open-source LLM-generated, will the detection model have easy access to the internal parameters used to generate this text? I don't think the authors should make too much of a distinction between closed-source and commercial models for the task of detecting LLM-generated text. So I suggest the authors to add some open-source models to the test models, which will make the conclusions more convincing, and I think the readers are also interested in the differences between texts generated by commercial closed-source models and open-source models. I understand the infeasibility of conducting new experiments in a short period of time, so I would suggest that the authors mention this in the limitations section. 3. The authors mention in question 8 of the checklist that they provide enough details about computational resource consumption in Section 5.1, but I didn't find them in the corresponding section. I think that for this kind of detection task, comparing the running efficiency of the proposed model and the competitors is also an important part. In particular, I'd be interested to know the resource consumption comparison between DPIC models and those that only input candidate text for classification.

Rating

7

Confidence

4

Soundness

3

Presentation

3

Contribution

3

Limitations

I think the statement made by the author in the limitations section (Appendix A) is not sufficient. It seems that the author is only analyzing the results of the experiment in the prompt reconstruction part by mentioning the possible scenarios that may occur when using the model. I would suggest that the authors flesh out this section from the perspective of the model's deployment in a real-world environment and its impact on society. Additionally, I suggest that the authors include an analysis with some of the current techniques that help AI-generated text escape detection, to test whether the model will be defeated by these models.

Reviewer eWrN2024-08-10

Thank you for the clarification, I am satisfied with it. In addition I would like the authors to include, in the limitations or conclusion section, an assessment of the risk of benchmark contamination in the evaluation process, which would make the analysis of the experimental results more robust, as can be seen in the following works. [1] Unveiling the Spectrum of Data Contamination in Language Models: A Survey from Detection to Remediation, ACL 2024. [2] Benchmark Data Contamination of Large Language Models: A Survey, arXiv 2024. [3] NLP Evaluation in trouble: On the Need to Measure LLM Data Contamination for each Benchmark, EMNLP Findings 2023.

Authorsrebuttal2024-08-12

Thank you for your response

We are delighted to learn that the reviewer is satisfied with our response! We have read the works you mentioned, and it is crucial to consider whether the benchmark might be contaminated during the evaluation process. We will add the assessment of the risk of benchmark contamination into the limitations and conclusion sections to strengthen our manuscript, as the reviewer suggested. Thank you again for the time and expertise you have invested in these reviews.

Reviewer Av5h7/10 · confidence 4/52024-07-11

Summary

This paper addresses the problem of detecting texts generated by large language models (LLMs), which is a crucial issue considering the potential misuse of such models. The authors propose a novel method, DPIC (Decoupling Prompt and Intrinsic Characteristics), which aims to extract the intrinsic characteristics of black-box models, as traditional detection methods requiring access to the model's interior are not feasible. DPIC uses an auxiliary LLM to reconstruct the prompt of a candidate text and regenerate a text from it, allowing the detector to focus on the intrinsic characteristics of the generative model. The similarity between the candidate and regenerated texts is then used as a detection feature. Results show that DPIC outperforms baseline methods, achieving an average improvement of 6.76% and 2.91% in detecting texts from different domains generated by GPT4 and Claude3, respectively.

Strengths

The paper presents a novel approach to distinguishing between machine-generated and human-written texts by decoupling intrinsic characteristics from prompts. This innovative method offers new insights into the essential differences between these two types of text, marking a significant contribution to the field. One of the major strengths of this approach is its applicability to proprietary models. Given the usual inaccessibility to model parameters, working with such black-box models is challenging. The paper also demonstrates robustness across various datasets, source models, and paraphrasing attacks, suggesting that the proposed method is capable of maintaining performance under different conditions and adversarial scenarios. Another significant strength is the method's performance in terms of AUROC. It achieves significantly higher AUROC scores compared to previous zero-shot methods, although the paper acknowledges that comparing a method requiring training to zero-shot methods may not be entirely fair.

Weaknesses

There are a few areas that could be improved. Firstly, the comparison with zero-shot methods seems potentially unfair since the proposed method requires training. Including trained detectors as baselines, for instance, using the same LLM used by DPIC to train a classifier directly, might provide a more balanced comparison. Secondly, the paper lacks a detailed analysis of the method's robustness on different lengths of text and languages. This could limit the applicability of the method in real-world scenarios. Lastly, the content of Section 3 appears misplaced as it discusses experimental settings rather than threat models. A reorganization or further clarification in this section would enhance the overall coherence of the paper.

Questions

Figure2, can we use a pre-trained Siamese Network to measure the similarity in DPIC? Then, we do not need a training here. LN121, the section 3 looks strange because it does not provide a threat model but some experimental settings. Table1, I would expect to see more comparsion with trained detectors given that DPIC is also a trained detector. Figure3, it seems the major contribution is from the supervised training, while the contribution from the prompt is much smaller. Why? Figure3, the improvement of DNA-GPT(prompt) compared to DNA-GPT(supervised) mainly happens on PubMed. Is it caused by the QA style of the dataset?

Rating

7

Confidence

4

Soundness

3

Presentation

3

Contribution

3

Limitations

Yes.

Reviewer XAPE6/10 · confidence 4/52024-07-12

Summary

This paper proposes a novel method named DPIC (Decoupling Prompt and Intrinsic Characteristics) for detecting texts generated by LLMs. The authors posit that generated texts are a coupled product of prompts and intrinsic characteristics, and suggest that decoupling these two elements can enhance detection quality and generalization ability. Specifically, the DPIC method employs an auxiliary LLM to reconstruct the prompt of the candidate text, and then uses this prompt to regenerate the text. By comparing the similarity between the candidate text and the regenerated text, the detector can better focus on the intrinsic characteristics of the generating model. Experimental results show that, compared to baseline methods, DPIC improves the detection of texts generated by GPT-4 and Claude-3 in different domains by an average of 6.76% and 2.91%, respectively.

Strengths

- A new perspective is proposed, improving detection performance by decoupling prompts and intrinsic characteristics, with strong motivation and description. More importantly, this method can handle black-box detection scenarios. - Experimental results demonstrate that the DPIC method significantly enhances detection quality and generalization ability, especially when dealing with black-box models.

Weaknesses

- DPIC involves multiple steps, including prompt reconstruction and text regeneration, which significantly increase computational costs and resource overhead in practical applications. An ablation analysis on the impact of the training sample size would help readers further understand and evaluate the DPIC method. - DPIC is essentially a supervised method and should be compared fairly with methods based on RoBERTa (not the OpenAI detector trained on GPT-2 but a RoBERTa classifier trained from scratch). - Supervised methods perform well within their domain but have poor out-of-distribution generalization ability, which lacks discussion in the paper. For example, the performance of DPIC trained on XSum on Writing, and the performance of DPIC trained on ChatGPT re-generated data on Claude-3. This is crucial for highlighting the effectiveness of DPIC in practical applications.

Questions

How is the accuracy of prompt reconstruction evaluated? Did the authors verify the consistency between the reconstructed prompts and the original prompts? If there is a significant difference between the reconstructed prompts and the original prompts, how much impact would that have on the detection results?

Rating

6

Confidence

4

Soundness

3

Presentation

3

Contribution

3

Limitations

The authors did not discuss the out-of-distribution generalization ability of DPIC.

Reviewer XAPE2024-08-09

Thanks for the clarification

Thanks for the clarification, which addresses some of my key concerns. I have revised my score accordingly. Honestly, the motivation for this paper is excellent. However, my main concern is whether the regenerated text consistently maintains a high semantic similarity with the original. I'm not entirely convinced yet. Providing more support and analysis on this point could strengthen the manuscript.

Authorsrebuttal2024-08-12

Official Comment by Authors

We sincerely appreciate your recognition of our paper's motivation. Below, I will answer your question on 'whether the regenerated text consistently maintains a high semantic similarity with the original.' We used the gte-Qwen1.5-7B-instruct model to extract embeddings from the original text and the regenerated text, and then measured their semantic similarity using cosine similarity. We evaluated 9 datasets and obtained the values of cosine similarity for Average, Standard Deviation, First Quartile, Second Quartile, and Third Quartile. To better understand the degree of semantic similarity reflected by the value of cosine similarity, we introduce the baseline similarity for reference, which is defined as the cosine similarity between embeddings of human and AI-generated texts for the same prompt. Since the texts correspond to the same prompt, their semantic similarity can be regarded as at a high level. As shown in the table below, the average similarity exceeds the baseline similarity across all 9 datasets, which indicates that the original and regenerated texts achieve high semantic similarity. Additionally, the standard deviation values range from 0.11 to 0.15, which is relatively small compared to the average semantic similarity. This indicates that most of the texts maintain a high level of semantic similarity with the regenerated text. I hope this explanation addresses your concern. If you have any further concerns or questions about our work, we are happy to discuss them with you. We will also add this part to strengthen the manuscript. Thank you again for the time and expertise you have invested in these reviews. | | ChatGPT | | | GPT4 | | | Claude3 | | | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | | XSum | Writing | PubMed | XSum | Writing | PubMed | XSum | Writing | PubMed | | Baseline Similarity | 0.5042 | 0.3739 | 0.5207 | 0.5065 | 0.3760 | 0.5225 | 0.2816 | 0.2538 | 0.5310 | | Average Similarity | **0.6201** | **0.4462** | **0.6672** | **0.5975** | **0.4367** | **0.6756** | **0.5928** | **0.4466** | **0.6877** | | Standard Deviation | 0.1357 | 0.1414 | 0.1367 | 0.1349 | 0.1336 | 0.1184 | 0.1358 | 0.1414 | 0.1333 | | First Quartile | 0.5320 | 0.3581 | 0.5963 | 0.5147 | 0.3441 | 0.6036 | 0.5047 | 0.3540 | 0.6159 | | Second Quartile | 0.6351 | 0.4468 | 0.6799 | 0.6023 | 0.4377 | 0.6881 | 0.5998 | 0.4492 | 0.6907 | | Third Quartile | 0.7192 | 0.5495 | 0.7644 | 0.6906 | 0.5340 | 0.7621 | 0.6992 | 0.5329 | 0.7927 |

Reviewer XAPE2024-08-13

Thanks for the response.

Thanks for your response and experiment. However, I am a little confused (can't fully understand) about the setting in the response experiment. I mean, maybe directly evaluating the similarity between the source text and the machine-generated text is enough to solve my concern?

Authorsrebuttal2024-08-13

Detailed Response by Author

Dear reviewer, your concern is whether the regenerated text **consistently** maintains a **high semantic similarity** with the original. We divided it into three aspects to address your concern: 1. **Semantic Similarity** To evaluate the **semantic similarity** between the source text and the machine regenerated text, we measured the **cosine similarity** of their corresponding embeddings. Take the XSum dataset generated by ChatGPT (The First Column) as an example, the average cosine similarity is 0.6201. --- 2. **High Semantic Similarity** There is an issue: given a value of cosine similarity, such as the previously mentioned 0.6201, does it indicate a high degree of similarity between the source text and the machine-generated text? To address this issue, we introduced a baseline similarity **for reference**, which better reflects the degree of semantic similarity reflected by a specific cosine similarity value. The baseline similarity for reference is defined as the cosine similarity between human and AI texts for the same prompt. Since the texts correspond to the same prompt, their semantic similarity can be regarded as high. For example, in the XSum dataset generated by ChatGPT, the baseline similarity is 0.5042, which means that 0.5042 of cosine similarity already represents a high level of semantic similarity. The average similarity between the source text and the machine regenerated text is 0.6201, higher than 0.5042, meaning that they have **high** semantic similarity. --- 3. **Consistently Maintains High Semantic Similarity** To evaluate whether the similarity between source text and the machine regenerated text **consistently** maintains a high semantic similarity. We measured the Standard Deviation, First Quartile, Second Quartile, and Third Quartile to better understand the distribution. - Standard Deviation: A measure of how dispersed the data is in relation to the mean. In the XSum dataset generated by ChatGPT, the standard deviation is 0.1357, which is relatively small compared to the average of 0.6201, indicating **minimal fluctuation**. Therefore, we can conclude that the regenerated text **consistently** maintains a high semantic similarity with the original. --- We greatly value every opportunity to discuss with you, **so we have conducted detailed experiments to address your concerns as thoroughly as possible.** I hope this explanation fully addresses your concern.

Reviewer XAPE2024-08-13

Official Comment by Reviewer XAPE

Thanks for the responses. I appreciate the author's detailed explanation, which addresses my concerns. I have revised my score accordingly.

Authorsrebuttal2024-08-13

Thank you for your response

We are delighted that our response addresses the reviewer's concerns. Again, we thank the reviewer for your valuable and positive feedback and comments.

Reviewer qTwx6/10 · confidence 4/52024-07-15

Summary

This paper develops an LLM-generated text detection method by ****. The key idea is to regenerate text based on a prompt reconstructed by an auxiliary LLM from the candidate text so that the regenerated text and the original candidate text can be used to extract similarity-based features, which are used for a classifier.

Strengths

- (S1) The idea is simple and intuitive. - (S2) Comprehensive experiments and analysis especially including paraphrased machine-generated text such as DIPPER and back-translate (in Table3) - (S3) The paper is well-written and easy to follow.

Weaknesses

- (W1) It is not clear if the proposed method can replace other classification-based methods. Ghostbuster [41] is known to be a strong machine-generated text detection method and should be compared for evaluation (it also offers a benchmark as well). Other recent simple-yet-effective methods could be compared as well. For example, - [Ref 1] Smaller Language Models are Better Zero-shot Machine-Generated Text Detectors https://aclanthology.org/2024.eacl-short.25.pdf - [Ref 2] Your Large Language Models Are Leaving Fingerprints https://arxiv.org/abs/2405.14057 - (W2) The datasets used for evaluation might be too easy to detect. Unless there’s a special reason, the proposed should also be tested in other benchmarks used for machine-generated text detection research (e.g., the Ghostbuster dataset). - (W3) The feature extraction is computationally expensive. Two LLM inferences (prompt generation, candidate text regeneration) and then dual-encoder-based feature extraction. It is not clear if the feature extraction offers significantly better benefits compared to more lightweight approaches (e.g., [Ref 1][Ref 2] above) ### Minor comments For perturbation, in addition to DIPPER, OUTFOX is another option. - [Ref 3] OUTFOX: LLM-Generated Essay Detection Through In-Context Learning with Adversarially Generated Examples https://arxiv.org/abs/2307.11729

Questions

Please answer the weaknesses raised in the Weaknesses section.

Rating

6

Confidence

4

Soundness

3

Presentation

3

Contribution

3

Limitations

Yes.

Reviewer qTwx2024-08-12

Thank you for sharing the new experiment results and the responses. My concerns have not been addressed and I keep my initial evaluation as 6: Weak Accept. >> (W1) & (W2) > > Actually, our benchmark used in our original paper, already covers two domains from the Ghostbuster benchmark, namely Xsum for news articles and Writing for creative story writing. In addition, our benchmark also includes multiple prompts and three generative large language models, offering a more rigorous evaluation standard. Therefore, to better compare the performance of these newly added methods with DPIC, we further tested these methods using the benchmark employed in our paper. Unless the Ghostbuster benchmark is a subset of the dataset, the Ghostbuster benchmark is considered another dataset and we cannot tell which one is better. The statement "offering a more rigorous evaluation standard." is not verified in the paper. Please clarify why the author(s) consider it. >> (W3) This concern is not addressed. The feature extraction is effective with a certain cost.

Authorsrebuttal2024-08-12

Official Comment by Authors

Thank you again for the time and expertise you have invested in these reviews. We appreciate the opportunity to address the concerns and questions raised. - **(W1) & (W2):** Unless the Ghostbuster benchmark is a subset of the dataset, the Ghostbuster benchmark is considered another dataset and we cannot tell which one is better. The statement "offering a more rigorous evaluation standard." is not verified in the paper. Please clarify why the author(s) consider it. **Response:** Dear reviewer, we sincerely apologize for comparing the benchmark merely through its domain, which is not full-considered. Since the Ghostbuster benchmark is not a subset of the our benchmark, it is meaningful to evaluate detectors on the Ghostbuster benchmark as well. Therefore, we will add the results on the Ghostbuster benchmark in the final version, and thanks again for your valuable suggestions. And the statement 'offering a more rigorous evaluation standard' refers to the statement that the benchmark used in our paper includes three large language models. Since cross-model detection is a challenging problem in generated text detection[1,2], we considered our benchmark is more rigorous in this aspect. From a strict perspective, we should not compare benchmark merely depending on the adopted LLMs. Therefore, we will add the results on the Ghostbuster benchmark in the final version, and not compare the benchmarks. --- - **(W3):** This concern is not addressed. The feature extraction is effective with a certain cost. **Response:** Dear Reviewer, since we presented comparisons with the methods you mentioned in Weaknesses 1 & 2 of our rebuttal, we did not directly respond to the statement in Weakness 3: 'It is not clear if the feature extraction offers significantly better benefits compared to more lightweight approaches (e.g., [Ref 1][Ref 2] above).' We apologize for any confusion this may have caused and appreciate the opportunity to clarify further. As shown in Table 1 of the attached PDF, we have compared our results with other methods, including the two lightweight methods you mentioned: Fingerprints [3], and Smaller Models [4]. To facilitate your review, we present the results below. Our method indeed shows a significant improvement over the lightweight methods in terms of average detection AUROC on both our benchmark and Ghostbuster benchmark. I hope this explanation addresses your concern. If you have any further concerns or questions about our work, we are happy to discuss them with you. We will also add this part to strengthen the manuscript. Thank you again for the time and expertise you have invested in these reviews. | | ChatGPT | | | | GPT4 | | | | Claude3 | | | | Ghostbuster | | | | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | | XSum | Writing | PubMed | Avg. | XSum | Writing | PubMed | Avg. | XSum | Writing | PubMed | Avg. | News | Creative Writing | Student Essays | Avg. | | Fingerprints | 0.8815 | 0.8073 | 0.6816 | 0.7901 | 0.8124 | 0.7896 | 0.7133 | 0.7718 | 0.8849 | 0.9033 | 0.8692 | 0.8858 | 0.8108 | 0.8373 | 0.7846 | 0.8109 | | Smaller Models | 0.9835 | 0.9713 | 0.8843 | 0.9464 | 0.8818 | 0.9098 | 0.8234 | 0.8717 | 0.9798 | 0.9594 | 0.8868 | 0.9420 | **0.9983** | 0.8957 | 0.9673 | 0.9537 | | DPIC | **1.0000** | **0.9821** | **0.9082** | **0.9634** | **0.9996** | **0.9768** | **0.9438** | **0.9734** | **1.0000** | **0.9950** | **0.9686** | **0.9879** | 0.9950 | **0.9978** | **0.9774** | **0.9900** | ## **References** [1] Bao G, Zhao Y, Teng Z, et al. Fast-DetectGPT: Efficient Zero-Shot Detection of Machine-Generated Text via Conditional Probability Curvature[C]//The Twelfth International Conference on Learning Representations. [2] Yang X, Cheng W, Wu Y, et al. DNA-GPT: Divergent N-Gram Analysis for Training-Free Detection of GPT-Generated Text[C]//The Twelfth International Conference on Learning Representations. [3] McGovern H, Stureborg R, Suhara Y, et al. Your Large Language Models Are Leaving Fingerprints[J]. arXiv preprint arXiv:2405.14057, 2024. [4] Mireshghallah N, Mattern J, Gao S, et al. Smaller Language Models are Better Zero-shot Machine-Generated Text Detectors[C]//Proceedings of the 18th Conference of the European Chapter of the Association for Computational Linguistics (Volume 2: Short Papers). 2024: 278-293.

Reviewer Av5h2024-08-12

Thanks for the clarification, which addresses my major concerns.

Authorsrebuttal2024-08-12

Thank you for your response

We are delighted that our response addresses the reviewer's major concerns. Again, we thank the reviewer for your valuable and positive feedback and comments.

Program Chairsdecision2024-09-25

Decision

Accept (poster)

© 2026 NYSGPT2525 LLC