Apply to my task
arXiv:2507.07251 ★ 70 Jul 9, 2025

Judge, Not Advisor: An LLM Recommends More Accurately by Scoring Ready-Made Candidates

Key result

LLMs are bad at answering "what do you recommend?". But they're great at something else: "here's a specific option — score it from -1 to 1." That's not a small wording tweak, it's a different task. The method lets you rank a list of ready-made options accurately — better than standard recommendation algorithms and better than a plain ChatGPT request. The trick: you don't ask the model to invent, you make it evaluate. You feed it a candidate, a detailed preference profile and a couple of examples with known scores. The model stops making things up and starts working with your data.

ALanguage-Driven Framework for Improving Personalized Recommendations: MergingLLMswith Traditional Algorithms

Key Aspects of the Research:

The study proposes a hybrid method for improving recommender systems (for movies, say). Instead of having the LLM come up with recommendations on its own, it's used as a "smart filter" to re-rank a list of candidates generated by a traditional algorithm. To do that, the authors build a very detailed prompt that includes the user's preferences in plain text, examples of their favorite movies, and metadata (preferences for rating, popularity, release year), and the LLM scores each candidate movie on a scale from -1 to 1.

Key Result: This approach, where the LLM doesn't generate but evaluates against clear criteria, beats both traditional algorithms and simple LLM queries in quality by a wide margin.


The Core of the Method, Explained:

The idea is to turn the LLM from an "advisor" into an "evaluator." Instead of asking the model to "recommend me something," we make it do a stricter and more useful job: "Here's my detailed profile, and here's a specific movie. Score how well it fits me."

This is done with an elaborate, multi-part prompt, which is the heart of the whole study.

The method for users:

  1. Define the role and the task: Tell the LLM clearly who it should be ("You are a recommendation expert") and exactly what to do ("Score the fit on a scale from -1.0 to 1.0 and answer with a number only"). That puts the model in an analytical frame of mind.

  2. Build a "preference profile": Don't stop at one sentence. Gather rich context about your tastes:

    • Direct request: A short description of what you're looking for ("I love sci-fi with deep philosophical themes").
    • Positive examples (few-shot): List 3-5 things you already like ("My favorite movies: 'The Matrix', 'Blade Runner'"). This is the single most important element; it "calibrates" the model's understanding.
    • Meta-preferences: Add extra rules and constraints ("I prefer highly rated movies," "I like popular movies," "I prefer movies made between 1980 and 2020").
  3. Provide the "candidate to evaluate": Describe the item to be scored clearly, using the same structure (title, description, rating and so on).

  4. Teach with examples (in-context learning): Right in the prompt, show the model 2-3 complete examples of how you yourself would score different movies (both a good match and a bad one). That teaches the model the scoring logic and the answer format.

In essence, you're not asking the LLM to find a needle in a haystack. You hand it a needle and a magnet (your profile) and ask how strongly they attract.


Practical Applicability:

  • Direct applicability: Very high. Anyone can take the prompt structure from the paper (Fig. 3) and adapt it to their needs in any chatbot (ChatGPT, Claude and others). Instead of movies, plug in books, bands, recipes, travel destinations. You can draw up your own list of 5-10 "candidates," ask the LLM to score each one, and then pick the winner.

  • Conceptual value: Huge. The study vividly proves a fundamental principle of prompt engineering: the quality of the context determines the quality of the result. You learn not just to "ask" but to "instruct," giving the model structured data, examples and constraints. That shifts the LLM interaction paradigm from conversation to task specification.

  • Adaptation potential: The method adapts easily. Just swap "movies" for any other kind of item and define the metadata that matters for it. For a restaurant recommendation that would be: cuisine type, price range, average rating, neighborhood, parking. The adaptation recipe: 1) Define the goal (say, pick a restaurant). 2) Build your "preference profile" (favorite restaurants, cuisine type, budget). 3) Find 3-5 candidates. 4) Ask the LLM to score each candidate on the scale, giving it your profile and the candidate's description.


A Practical Example:

You are a seasoned board game consultant. Your task is to evaluate how well a specific game matches a user's preferences.

Always answer with a number from -1.0 to 1.0 only, where:
-1.0: a complete mismatch.
0.0: neutral or not enough information.
1.0: a perfect match.

---
**EXAMPLE 1:**
**User profile:**
*   **Request:** "We're looking for a game for a group of 4-5 people. We love co-op games where you solve problems together. We don't like games where one person gets knocked out and has to sit around until the end."
*   **Favorite games:** "Pandemic", "Forbidden Island".
*   **Preferences:** Short sessions (under 60 minutes), simple rules.

**Game to evaluate:**
*   **Title:** "Mafia"
*   **Description:** A team-based psychological, turn-based role-playing game with a detective plot, modeling the struggle of an organized minority whose members know each other against an unorganized majority. Players are eliminated as the game goes on.

**Your score:**
-0.8

---
**EXAMPLE 2:**
**User profile:**
*   **Request:** "Looking for a deep two-player strategy game. I love building up my own civilization or economy. Happy to dig into complex rules."
*   **Favorite games:** "7 Wonders Duel", "Scythe".
*   **Preferences:** High replayability, minimal luck.

**Game to evaluate:**
*   **Title:** "Catan"
*   **Description:** Players take on the role of peaceful settlers colonizing the island of Catan. You gather resources and build settlements and cities. Winning depends heavily on dice rolls.

**Your score:**
0.2

---
**NOW YOUR TASK:**

**User profile:**
*   **Request:** "Need a fun, fast party game for a big group (6+ people). The point is laughs and socializing, not deep strategy."
*   **Favorite games:** "Codenames", "Alias", "Dixit".
*   **Preferences:** Simple rules you can explain in 5 minutes, lots of player interaction.

**Game to evaluate:**
*   **Title:** "Exploding Kittens"
*   **Description:** A highly strategic, kitty-powered game of chance with a loaded deck. Players draw cards until someone draws an Exploding Kitten, at which point they explode, are out of the game, and lose. You can play other cards to peek at the deck, force an opponent to draw extra cards, or shuffle the deck.

**Score how well this game matches the user's interests (answer with a number in the range [-1.0, 1.0] only):**

Why It Works:

This prompt is effective because it doesn't ask the LLM for vague advice; it makes it run a structured analysis by analogy:

  1. Role and output format: The instruction "You are a seasoned consultant" plus "answer with a number only" switches the model from chatbot mode to analytical-tool mode.
  2. Learning from examples (few-shot): The "Mafia" and "Catan" examples don't just show the answer format. They "calibrate" the model: it sees that player elimination is a negative for the first user (score -0.8) and heavy luck is a negative for the second (score 0.2).
  3. Decomposed preferences: The user profile is split into three parts: the general request, concrete examples ("Favorite games") and explicit constraints ("simple rules"). That gives the model rich, multi-faceted context, letting it grasp the "spirit" of the preferences rather than just keywords.
  4. A focused task: Instead of the open question "what do you recommend?", we ask a closed one: "score this." That lowers the chance of hallucinations and makes the model work with the data provided rather than its general knowledge.

Another Practical Example

You are an AI assistant for choosing online courses. Your task is to evaluate how well a specific course fits the user's goals and preferences.

Always answer with a number from -1.0 to 1.0 only, where:
-1.0: a complete mismatch.
0.0: neutral or not enough information.
1.0: a perfect match.

---
**EXAMPLE 1:**
**User profile:**
*   **Goal:** "I'm a junior marketer and want hands-on social media marketing skills. I need a structured program with homework and feedback from a mentor."
*   **What worked before:** Took a design fundamentals course on Coursera, loved the clear structure and the certificate.
*   **Preferences:** Video lectures, hands-on assignments, a mentor, a final portfolio project.

**Course to evaluate:**
*   **Title:** "Social Media Marketing for Business in 30 Days"
*   **Description:** An intensive course of 10 recorded webinars. Access to a private community chat with other participants. No homework or grading.

**Your score:**
-0.5

---
**NOW YOUR TASK:**

**User profile:**
*   **Goal:** "I'm an experienced developer and want to get up to speed fast on a technology that's new to me: Docker. I don't need fluff or basics, I need a concentrated dose of expert knowledge I can put to work right away."
*   **What worked before:** Bought short, dense Udemy courses on specific frameworks.
*   **Preferences:** Short lectures (5-15 minutes), practice-focused, no homework, lifetime access to materials.

**Course to evaluate:**
*   **Title:** "Docker and Kubernetes: The Complete Beginner's Guide"
*   **Description:** A comprehensive 40-hour course. Covers networking basics and working with Linux in detail. The first 10 hours are theory for newcomers. The course includes weekly graded homework.

**Score how well this course matches the user's interests (answer with a number in the range [-1.0, 1.0] only):**

Why This Example Works, Mechanically.

This example works on the same principles as the previous one, but in a different domain, which proves the approach is universal:

  1. Context through role: "An AI assistant for choosing online courses" sets the right frame for the analysis immediately.
  2. Understanding through contrast: The task pits the profile of an "experienced developer" who wants a "concentrated dose of knowledge" against a course "for beginners" that covers "basics in detail." Having learned from the first example, the model easily picks up the mismatch.
  3. The weight of "negative" preferences: The "no homework" note in the user profile becomes a key factor in the low score for a course where homework is part of the program. That teaches the user to spell out not only what they want but also what they want to avoid.
  4. A real-world analogy: The method mimics how people actually decide. We don't search for the "perfect course" in a vacuum. We find a few options and compare them one by one against our internal "checklist" of requirements. This prompt simply formalizes that process for the LLM.

Usefulness Score: 92

02

Core Evaluation Criteria

  • A. Relevance to prompting techniques: Yes. The paper is a detailed blueprint for building a complex, structured prompt that makes the LLM perform an evaluation task rather than mere generation.
  • B. Better conversational answers: Yes. The method directly targets more personalized and relevant answers (recommendations), which is a key aspect of quality.
  • C. Direct practical applicability: Yes. A user can't recreate the whole system (with SVD algorithms), but they can fully copy and adapt the prompt's logic and structure to get high-quality recommendations in a regular LLM chat.
  • D. Conceptual value: Very high. The paper clearly shows why supplying rich, structured context (preferences, examples, metadata) is far more effective than simple requests.
  • E. A useful new practice (clusters): The work hits several key clusters at once:
    • No. 1 (Phrasing techniques): Using few-shot examples to teach the model a task "on the fly."
    • No. 3 (Structure optimization): A showcase of a highly structured prompt with clear sections.
    • No. 5 (Extraction and structuring): The prompt aims to extract a specific numeric value (the score).
    • No. 6 (Context and memory): The whole method rests on effectively feeding in context about the user's preferences.
  • Practicality checklist (+15 points): Yes, every item on the checklist is touched on to some degree. The work gives ready-made constructs, shows how to structure a request, and reveals how to make an LLM do an analytical rather than descriptive task.
03

Numeric Usefulness Score

Arguments for a high score (92/100): This paper is a genuine masterclass in prompting for complex judgment and evaluation tasks. It offers not just an idea but a ready, reproducible template (Fig. 3 in the paper) you can adapt to any field, from picking books and music to planning trips and choosing a hobby. The key value for users is seeing how to move from simple requests ("recommend a movie") to building a detailed "preference profile" right in the prompt, which dramatically improves answer quality. It's one of the most useful techniques for an advanced user.

Counterarguments (why not 100): * System focus: The paper's main focus is the hybrid system (SVD + LLM), not just prompt engineering. A less experienced user may conclude the method is useless without access to such complex systems, when in fact the value lies precisely in the prompt structure, which works with any LLM. * Requires adaptation: The template is universal, but applying it to other areas takes thought and adaptation: the user has to figure out which "metadata" (counterparts of IMDb rating or popularity) matter for their task.


Research digest

Key result

LLMs are bad at answering "what do you recommend?". But they're great at something else: "here's a specific option — score it from -1 to 1." That's not a small wording tweak, it's a different task. The method lets you rank a list of ready-made options accurately — better than standard recommendation algorithms and better than a plain ChatGPT request. The trick: you don't ask the model to invent, you make it evaluate. You feed it a candidate, a detailed preference profile and a couple of examples with known scores. The model stops making things up and starts working with your data.

Principle

The standard approach: "recommend something similar to 'The Matrix'." The model spits something out — somewhat plausible, somewhat off. This method: first you gather 5-10 candidates any way you like. Then for each one you give the model three things: a preference profile (what you love + concrete examples + constraints), the candidate's description, and 2-3 calibration examples with known scores. The model answers with a number from -1.0 to 1.0. Nothing else. A closed question about a specific item is a fundamentally different task for the model. It works with what you gave it instead of rummaging through its own associations. The preference profile has three layers: a direct request in words ("looking for a dark crime drama"), favorite examples ("I like 'Peaky Blinders', 'True Detective'"), and meta-rules ("only if rated above 8, nothing before 2010"). Together the three layers give the model the "spirit" of your preferences, not just keywords.

Why it works

The open question "what do you recommend?" is a request to generate from nothing. The model leans on general knowledge and averages out. Result: popular picks you already know, or random guesses. The closed question "score this" is an analytical task. The model compares a specific item against a specific profile. No guessing needed; there's data to work with. The odds of inventing things that aren't there drop sharply. The calibration examples in the prompt are the key element. You show the model your scoring logic on two cases: one that's obviously a fit (score 0.8) and one that obviously isn't (score -0.7). The model picks up which factors actually matter to you. Without these examples the model guesses your criteria. With them, it applies yours. Splitting the profile into three parts (request + examples + constraints) isn't random either. It reduces the weight of any single poorly worded sentence. If the request is "fuzzy," the examples sharpen it. If the examples are "broad," the constraints narrow them.

When to apply

Any choice from a list of candidates: movies, series, books, online courses, restaurants, board games, tools, vendors. Works especially well when you have 5-20 candidates and need to prioritize them. Or when you already know a few options but don't know where to start. NOT a fit: when there are no candidates at all and you need discovery from scratch. The method evaluates, it doesn't search — it won't pull a needle out of a haystack, but it will tell you which of three needles is sharpest.

Mini recipe

1. Set the role and output format: "You are an expert in [field]. Score the fit on a scale from -1.0 to 1.0. Answer with a number only." That switches the model from chit-chat mode to analysis mode. 2. Build a three-layer preference profile: — Direct request: "Looking for [what exactly] with [key traits]" — Favorite examples: 3-5 specific things you already like — Meta-rules: constraints on date, rating, format, budget — anything that matters 3. Add 2 calibration examples right in the prompt: one obviously good candidate scored 0.7-0.9, one bad one scored between -0.5 and -0.9. Show the model your logic — don't tell it, demonstrate it. 4. Find 5-10 candidates: via search, word of mouth, catalogs, or another request to the same model. They don't need to be perfect — you just need options to compare. 5. Run each candidate through: paste the profile + the candidate's description + ask for a score. One request or one at a time — doesn't matter. 6. Sort by score and start with anything above 0.6.

Examples

[BAD]: `Recommend me a TV series, I like crime shows` [GOOD]: `You are a TV series expert. Score from -1.0 to 1.0 how well a series fits the user. Answer with a number only. User profile: — Request: psychological thrillers with unexpected twists, atmosphere matters more than action — Favorites: "Dark", "Peaky Blinders", "True Detective S1" — Constraints: no more than 3 seasons, IMDb rating 8.0+, no gratuitous violence EXAMPLE 1: Series: "Black Mirror" — an anthology about society and technology, psychological tension, minimal violence, IMDb 8.8 Score: 0.8 EXAMPLE 2: Series: "Intercept" — a crime action show built around chases and shootouts, 4 seasons, IMDb 7.1 Score: -0.6 NOW SCORE: Series: "The Detained" — a mystery, 6 episodes, slow-burn tension, flashbacks, a surprise ending, IMDb 8.4, no action scenes Score:`

In plain words

Traditional recommender systems are dumb calculators: they look at your past clicks and try to push something similar. The problem is they don't get context: if you bought a drill, you don't need ten more drills, you need drill bits or a shelf. Paper 2507.07251 proposes crossing these old-school algorithms with LLMs, so the model acts as the "brain" that understands the user's logic while classic code plays the "librarian" who searches the database fast.

Imagine walking into a huge bookstore staffed by a robot that can't hear a word you say and a very smart but slow sales clerk. The robot can sprint past every shelf in a second but can't tell "I want something sad" from "I want a textbook on the psychology of depression". In this framework the clerk (LLM) first analyzes your tricky request, translates it into clear parameters, and then sends the robot to fetch specific stacks of books. Technically both are working, but the result is an order of magnitude more on-point.

The key is that the LLM doesn't just guess; it uses structured analysis by analogy. It takes your profile, finds hidden patterns in it and forms a hypothesis: "this user doesn't just like sci-fi, they like space survival stories with a heavy biology angle." Then the traditional algorithm kicks in and filters millions of items by those exact criteria. The hybrid removes the main weaknesses of LLMs: their tendency to hallucinate and their sluggishness with big data.

It was tested on product recommendations, but the principle is universal. You can stretch this scheme over social media content feeds, music discovery or even corporate knowledge bases. Anywhere there's a mountain of data and a picky user, the "smart interpreter + fast search engine" combo beats any attempt to make an LLM do everything solo. Product SEO turns into semantic matching, where what counts isn't the number of keywords but how precisely the description fits the model's logic.

Bottom line: the era of simple "by price" and "by popularity" filters is ending. The future belongs to systems that understand why you're searching and can quickly dig the right thing out of the junk pile. If your business still recommends products on a "customers also bought" basis, you've already lost to those rolling out a Language-Driven Framework. Either you teach your algorithms to understand human language, or your customers will leave for places that get them from half a word.

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 Judge, Not Advisor: An LLM Recommends More Accurately by Scoring Ready-Made Candidates arXiv:2507.07251

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.