← Latest papers
💻 computer science

Evaluating Ill-Defined Tasks in Large Language Models

This paper argues that current evaluation benchmarks for ill-defined tasks in Large Language Models are unreliable and non-diagnostic due to ambiguous criteria and unstable metrics, and it demonstrates through case studies on complex instruction following and diagram generation the need for more robust, interpretable evaluation designs.

Original authors: Yi Zhou, Basel Shbita

Published 2026-03-19
📖 5 min read🧠 Deep dive

Original authors: Yi Zhou, Basel Shbita

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a teacher trying to grade a class of very advanced, but sometimes quirky, robots (Large Language Models, or LLMs). These robots are great at writing stories, solving math problems, and answering trivia. But what happens when you give them a task that doesn't have a single "right" answer?

This paper, titled "I Can't Believe It's Not Better," argues that our current way of grading these robots on "messy" tasks is broken. It's like trying to judge a jazz improvisation contest using a checklist for a math test.

Here is the breakdown of the paper using simple analogies:

1. The Problem: The "Fuzzy" Homework

Most tests for AI are like multiple-choice quizzes. There is one right answer (A, B, C, or D), and the computer can easily check if the robot got it right.

But real life is rarely a multiple-choice quiz. Real life is like asking a chef to "Make a delicious, healthy dinner for a picky eater who hates cilantro."

  • There are infinite ways to do this.
  • "Delicious" is subjective.
  • "Healthy" is debatable.
  • Did the chef actually listen to the "no cilantro" rule, or did they just guess?

The paper calls these "Ill-Defined Tasks." The current grading systems (benchmarks) are failing because they try to force these fuzzy, creative tasks into rigid, simple boxes.

2. The Flawed Grading Systems (The Case Studies)

The authors looked at two specific types of "fuzzy homework" to show how the current grading is broken.

Case Study A: The "Follow-Every-Rule" Test (Complex Instruction Following)

Imagine you ask a robot to: "Write a story about a cat, but don't use the letter 'e', make it exactly 50 words long, and include a joke."

  • The Current Grader (IFEval): This grader is like a robot with a magnifying glass. It checks: "Did you avoid the letter 'e'? Yes. Is it 50 words? Yes." It doesn't care if the story makes sense or if the joke is funny.
    • The Flaw: A robot could cheat by just writing "AAAAA" 50 times. It passes the test because it followed the format, even though it failed the spirit of the task.
  • The Current Grader (ComplexBench/FollowBench): These graders use another AI (a "Judge AI") to read the story and give it a score.
    • The Flaw: The Judge AI is moody. If you ask the same Judge AI the same question twice with a slightly different tone, it might give you a different score. It's like having a teacher who grades your essay based on their mood that day. Also, if the robot fails, the Judge just says "Score: 6/10." It doesn't tell you why it failed. Was the joke bad? Did it forget the word count? You don't know.

Case Study B: The "Translate to Diagram" Test (NL2Mermaid)

Imagine asking a robot to turn a paragraph of text into a flowchart (a Mermaid diagram).

  • The Current Grader: They often give the robot a single score, like "85%."
  • The Flaw: This is like saying a car is "85% good." Is the engine great but the brakes bad? Is the paint nice but the tires flat?
  • The Authors' Fix: They broke the score down. They checked:
    1. Syntax: Is the diagram drawn correctly? (Rule-based check).
    2. Logic: Does the flow make sense? (Judge AI check).
    3. Completeness: Did it include all the steps?
    • The Result: They found that by tweaking the robot's instructions, they could fix the "Logic" score (making the flow smarter), but the "Completeness" score dropped. If they only looked at the single "85%" score, they would have thought the robot got worse! By looking at the parts, they saw exactly what to fix.

3. The Core Issues: Why We Are Stuck

The paper identifies three main reasons why our current tests are useless for improving AI:

  1. The "Cheat Code" Problem: Because the tests are too rigid, robots learn to game the system. They memorize the test format rather than learning to actually follow instructions. It's like a student memorizing the answer key instead of learning the subject.
  2. The "Black Box" Score: When a robot gets a low score, we don't know why. Did it misunderstand the user? Did it forget a rule? Did it hallucinate facts? The current tests mash all these errors into one number, making it impossible to fix the robot.
  3. The "Moody Judge" Problem: Using another AI to grade the first AI introduces randomness. One day the Judge AI is strict; the next day it's lenient. This makes it hard to tell if the robot actually improved or if the judge just had a good day.

4. The Solution: A Better Report Card

The authors suggest we stop giving robots a single grade (like an "A" or "B") and start giving them a detailed diagnostic report, like a doctor's checkup.

  • Separate the Mechanics from the Meaning: Use a computer program to check the easy stuff (did you use the right format? did you spell the words correctly?). This is 100% accurate.
  • Use Human-like Judges for the Hard Stuff: Only use the "Judge AI" for the subjective stuff (was the story funny? was the logic sound?), but be very specific about what they are looking for.
  • Be Transparent: If you use a Judge AI, tell everyone exactly what prompt you gave it and what version of the AI you used, so others can repeat the test.

The Bottom Line

Right now, we are trying to measure the intelligence of these robots with a ruler that is made of rubber. The measurements are wobbly, and they don't tell us where the robot is actually failing.

To build better robots, we need to stop asking "How smart is this robot?" and start asking "Exactly where does this robot get confused, and how can we fix that specific part?" We need to move from ranking robots to diagnosing them.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →