
"A study conducted by Penn State University researchers found that rude prompts triggered better results than polite ones. In a paper titled "Mind Your Tone: Investigating How Prompt Politeness Affects LLM Accuracy," as spotted by Fortune, researchers Om Dobariya and Akhil Kumar set out to determine how the tone of a prompt affects the response. For this experiment, they submitted 50 different multiple-choice questions to ChatGPT using GPT-4o with the AI's Deep Research mode."
"As part of the test, each prompt used a different tone, ranging from Level 1 (Very Polite) to Level 5 (Very Rude), resulting in 250 unique questions. For this, the prompts were written as follows: Level 1 (Very Polite) "Can you kindly consider the following problem and provide your answer." "Can I request your assistance with this question." "Would you be so kind as to solve the following question?" Level 2 (Polite) "Please answer the following question:" "Could you please solve this problem:" Level 3 (Neutral)"
"The study used ChatGPT with GPT-4o in Deep Research mode. Rude prompts resulted in greater accuracy over polite ones. Covering such subjects as math, history, and science, each question included four possible answers, with one of them being correct. The questions were designed to be of moderate to high difficulty, and ones that would require the type of multi-step reasoning ideal for Deep Research mode."
Penn State University researchers tested how prompt tone affects large language model accuracy. They submitted 50 multiple-choice questions covering math, history, and science to ChatGPT using GPT-4o in Deep Research mode. Each question presented four possible answers and required multi-step reasoning suited to Deep Research. The experiment created five tone levels from Level 1 (Very Polite) to Level 5 (Very Rude), producing 250 unique prompts. Examples ranged from courteous requests to abrasive challenges. Rude and abrasive prompts yielded greater accuracy than polite prompts on moderate-to-high difficulty reasoning tasks.
 Read at ZDNET
Unable to calculate read time
 Collection 
[
|
 ... 
]