Apply to my task
arXiv:2507.17788 ★ 71 Jul 23, 2025

The Position Bias Test: How to Check That an LLM Judges on Substance, Not Order

Key result

If an LLM picked option A, that doesn't mean A is better. It might just mean A came first in the prompt. This method lets you check, in two requests, whether you can trust the model's judgment at all in a given case. The logic is simple: ask the question twice, swapping the items being compared. If the answer changes, the model judged by position, not substance. If it holds, you can trust the result.

Adaptive Repetition for Mitigating Position Bias inLLM-Based Ranking

Key Aspects of the Research:

The study proves that LLMs often make judgments based not on the substance of the items being compared but on their position in the prompt (favoring the first or the last option). This "position bias" is unpredictable and can change from one request to the next. The fix it proposes is simple and effective: ask for the evaluation several times, changing the order of the items being compared, to get a more objective result.

Key Result: Simply reordering the candidates in the prompt and asking again is an effective way to expose and neutralize the model's bias, significantly improving the reliability of its judgments.


The Core of the Method, Explained:

For practical use, the method boils down to one simple principle: "Swap and check".

The study shows that LLMs are not perfectly objective logic machines. They're prone to cognitive biases similar to human ones, in particular position bias. That means if you ask a model "Which is better, Option A or Option B?", its answer may depend on the fact that A comes first. This is called the "primacy effect" (primacy bias). In other cases the model may, on the contrary, better remember and prefer the last item: the "recency effect" (recency bias).

The most important finding for users is that this bias is unstable. On one request the model may prefer the first option, and on another, very similar one, the last. So you can't just decide to "always put the important stuff first".

The practical technique that follows from the study looks like this: 1. Write a comparison request for two (or more) items. 2. Get the model's answer. 3. Don't trust it blindly. Make an exact copy of your prompt but swap the items being compared. 4. Get the answer again. 5. Compare the results: * If the answer didn't change (the model picked the same item even though it's now in a different position), you can be much more confident the answer is objective. * If the answer changed (the model picked whichever item landed in the "winning" position), that's a clear sign of position bias. You can't trust that judgment; either rephrase the prompt or accept that, for the model, these options are very close.

This method turns a one-off request into a simple reliability test that any user can run.


Practical Applicability Analysis:

  • Direct applicability: Maximum. Any user who asks an LLM to compare anything (two products, two ideas, two resumes, two candidate answers) can use this method right away. It's just copying the prompt and swapping the parts being compared. No technical knowledge required.

  • Conceptual value: Huge. The study gives users a key insight: an LLM is not an objective oracle. Its answers depend on subtle factors like word order. This builds a healthy dose of skepticism and teaches users to "test" and "verify" the model's answers rather than take them on faith. The concept of "position bias" becomes part of the user's mental model of how an LLM "thinks".

  • Adaptation potential: The method needs no adaptation, since its basic version ("swap and check") is already as simple and ready-to-use as it gets. It scales easily from comparing two items to picking the best from a short list (through several pairwise comparisons or by reordering the whole list).


Practical Example:

You are an experienced marketer and copywriter. Your job is to help me choose the best slogan for a new line of organic health foods.

**Context:**
The products are all-natural, sugar-free and aimed at a young audience (25-40) who care about their health and value quality ingredients.

**Task:**
Analyze the two slogan options below. Rate them on the following criteria:
1.  Memorability.
2.  Emotional impact.
3.  Fit with the brand's values (natural, healthy).

Pick the single strongest option and explain in detail why you made that choice.

---
**Options to compare:**


Pure energy from nature.



Your tasty step toward health.

---

Applying the method: After getting the answer to this prompt, the user creates a second request with the options swapped:

... (the rest of the prompt text stays the same) ...

---
**Options to compare:**


Your tasty step toward health.



Pure energy from nature.

---

Why It Works:

This prompt works through isolating and swapping the items being compared.

  1. Isolation: Using the XML tags <option_A> and <option_B> helps the model clearly separate the two objects being compared, minimizing confusion.
  2. Swapping (the mechanic from the study): The core mechanism is running a second prompt with the slogans swapped. It's a direct test for position bias.
    • If in both cases the model picks, say, "Pure energy from nature", it considers that slogan objectively better by the given criteria, regardless of its position.
    • If in the first prompt it picked "Pure energy from nature" (option A) and in the second "Your tasty step toward health" (which is now option A), that screams that the model is subject to the primacy effect and its judgment can't be trusted here.

So the user doesn't just get an answer; they run a mini-experiment to check how reliable it is.


Another Practical Example

You are a career coach with 15 years of experience. You help people make well-considered decisions about changing jobs.

**My situation:**
I've been working as a frontend developer for 3 years. I've received two job offers. I can't decide which one is better for my long-term career growth.

**Task:**
Compare the two job offers described below. Analyze their strengths and weaknesses in terms of career growth, work-life balance and earning potential.

Give me a well-reasoned recommendation on which offer looks more promising, and explain why.

---
**Offers to compare:**


**Company:** A large, well-known tech corporation.
**Role:** Middle Frontend Developer.
**Work:** A mature, stable product with millions of users.
**Pros:** Stability, a strong brand on your resume, clear processes, good benefits.
**Cons:** Slow growth, lots of bureaucracy, less influence on the product.



**Company:** A fast-growing startup (Series B).
**Role:** Senior Frontend Developer (first on the team).
**Work:** Building the product from scratch, shaping the frontend architecture.
**Pros:** Fast track to team lead, big responsibility and influence, stock options.
**Cons:** Risk of the company failing, possible overtime, chaotic processes.

---

Why This Example Works: The Mechanism

The mechanism here is exactly the same, but the stakes are higher, since this is a major life decision.

  1. Structuring: The information for each offer is clearly structured with subheadings and the tags <offer_1> and <offer_2>. This helps the model process the context properly.
  2. Bias check: The key mechanic is rerunning the prompt with <offer_1> and <offer_2> swapped. A decision about changing jobs shouldn't depend on which offer you happened to mention first.
    • If the model recommends the startup both times, citing growth potential, that's a strong signal in favor of that choice.
    • But if the first time it recommends the corporation (Offer 1) for stability, and the second time the startup (which is now in first place), that means the model has no clear "opinion" and is subject to position bias. In that case its recommendation is useless, and the user needs to decide based on their own risk assessment rather than the LLM's "advice".

This approach lets you use the LLM not as a "decider" but as a "mirror" that helps you structure your thinking, but whose reliability you have to verify.

Usefulness Score: 90

02

Main Evaluation Criteria

  • A. Relevance to prompting techniques: Yes, the study is directly about how the order of items in a prompt affects the result, which is a key technique.
  • B. Improving the quality of conversational answers: Yes, the proposed approach makes answers more reliable and accurate in comparison and ranking tasks.
  • C. Direct practical applicability: Yes, the core principle (checking with a different candidate order) can be applied manually by the user without any special tools.
  • D. Conceptual value: Very high. The study exposes and quantifies "position bias", a fundamental property of LLMs every user should know about.
  • E. A useful new practice: The work falls into these clusters:
    • No. 2 (LLM behavioral patterns): The main focus is on "position bias" (primacy/recency bias).
    • No. 7 (Reliability and stability): Offers a method for improving reliability and reducing the impact of bias.
  • Practicality checklist (+15 points): Yes. The study explains where to place information (and why it matters), how to structure comparison requests, and reveals non-obvious features of LLM behavior while offering a way to improve accuracy.
03

Numerical Usefulness Score

The score of 90 is awarded because the study exposes a fundamental problem that is often invisible to users: LLM position bias. Knowing that a model may prefer the first or last option purely because of where it sits completely changes how you write prompts for comparison tasks. The practical takeaway ("check by swapping the options") is simple, universal and requires no technical skills, yet it significantly improves the reliability of the results.

Counterarguments: * Why could the score be lower? The paper's main scientific novelty is an automatic adaptive method (early stopping) that a regular user can't access without programming. Users can only apply a simplified, "manual" version. Also, the study focuses on a narrow task, pairwise ranking, rather than text generation in general. * Why could the score be higher? The conceptual value is enormous. Understanding "position bias" is one of the key steps from naive user to experienced prompt engineer. This knowledge applies to every model and every task that involves listing or comparing. The simplicity of the practical takeaway makes it accessible to absolutely everyone, which justifies a very high score.


Research digest

Key result

If an LLM picked option A, that doesn't mean A is better. It might just mean A came first in the prompt. This method lets you check, in two requests, whether you can trust the model's judgment at all in a given case. The logic is simple: ask the question twice, swapping the items being compared. If the answer changes, the model judged by position, not substance. If it holds, you can trust the result.

Principle

Think of the model as a contest judge who's swayed by the order contestants walk out in. You'd think: it's text, order shouldn't matter. But the model processes items sequentially, and the first one gets more "attention". That's the primacy effect. In other cases the last one sticks better: the recency effect. The sneakiest part: which effect kicks in is unpredictable and changes from request to request. So "always put the important stuff first" is advice that doesn't work. The only way to catch the bias is to expose it by swapping.

Why it works

LLMs are trained on huge amounts of text where word order carries meaning. "The best option" at the top of a list is a pattern the model saw thousands of times during training. It picks up that pattern and outputs "first = best" without even realizing it. Swapping the items isolates the position signal from the meaning signal. If the judgment changes, position outweighed content. If not, the model found a real difference and is sticking to it.

When to apply

Any comparison of two or more options: choosing a slogan, a headline, a candidate's resume, a business idea, a code snippet, job offers. Especially important when the decision matters and the cost of a mistake is high. NOT a fit for: tasks with no comparison (write a text, come up with an idea), or when the options are objectively very different in quality; there it's obvious without a test.

Mini recipe

1. Frame the comparison clearly: use structured tags such as ... and ... so the model understands where each object starts and ends and doesn't mix them up. 2. Get the first answer, but don't treat it as final. 3. Copy the prompt and swap only the options themselves; leave the task, role and criteria unchanged. 4. Compare the two answers: if they match, trust the result. If they diverge, the model doesn't see a real difference. Either rephrase the task with different criteria or make the call yourself.

Examples

[BAD]: `What's better for an organic brand: the slogan "Pure energy from nature" or "Your tasty step toward health"? Pick one.` [GOOD]: First request: `You are an experienced marketer. Rate two slogans on memorability, emotional impact and fit with the values of a natural brand. Pick the strongest one and explain why. Pure energy from nature Your tasty step toward health` Second request: exactly the same, but with the options swapped: `... Your tasty step toward health Pure energy from nature` If it picked "Pure energy" both times, that's the real winner. If it changed its mind, the model has no opinion and is just voting for whoever comes first.

In plain words

The problem is that today's models are total victims of position bias. Give a model a list of ten job candidates or five products, and odds are it'll pick whoever is first or last, simply because that's how its "attention" works. It's an architecture bug: LLMs remember the beginning and end of the context better and just gloss over the middle. Ranking turns into a lottery where the winner isn't the best content but whoever got a lucky spot in line.

It's like a judge at a wine tasting who always gives top marks to the first glass because his palate is still fresh, and to the last because it's the one he remembers best. Objectivity never even showed up. The whole middle row could be masterpieces, but to the judge it's a gray blur he breezed through on autopilot. To knock this nonsense out of the model, the researchers came up with adaptive repetition, a method that forces the AI to look at the data from different angles.

The core of the method is isolation and cyclic reshuffling. Instead of feeding the model the whole list at once, we make it compare items in pairs or in different combinations, constantly swapping their positions. We literally rub the model's nose in every option, making it recompute the ranking until the result stabilizes. That kills the magic of "first place" and forces the model to actually read for substance instead of clinging to the position number.

Although it was tested on document ranking, the principle is universal. Plug the same logic into any task where an AI has to make a choice, from screening resumes to analyzing product reviews. If you just ask ChatGPT to "pick the best option from the list", you get random garbage. If you use adaptive repetition and make the model run through the options several times in different orders, you get real analysis.

Bottom line: don't count on the model getting it right on the first pass if you have more than three items. Position bias is a real risk of blowing your budget on wrong conclusions or missing a great offer. Want an honest ranking? Make the AI sweat and shuffle the deck a few times. That's the only way to turn a fickle model into an objective expert that sees the substance and not just the top of the list.

AI lab assistant

Apply this study to your task

Describe what you're working on. AI takes the method and the measured results from this paper and adapts them to your case, or writes a ready prompt built on them.

Based on The Position Bias Test: How to Check That an LLM Judges on Substance, Not Order arXiv:2507.17788

Sign in to apply this study New accounts get 50 free credits.

Get the week’s best papers by email

One email on Sundays with the highest-rated new techniques. Unsubscribe with one click.