← Latest papers
🤖 machine learning

Offline Preference-Based Trajectory Evaluation

This paper proposes a preference-based trajectory evaluation method that compares agentic systems through temporal progress and time-to-return profiles, significantly reducing comparison ties and improving statistical efficiency compared to traditional terminal-success metrics that often lead to benchmark saturation.

Original authors: Fernando Diaz

Published 2026-06-17
📖 4 min read☕ Coffee break read

Original authors: Fernando Diaz

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 coach trying to decide which of two athletes is better at running a marathon.

The Old Way (Success Rate)
Currently, most AI systems are judged like this: You watch them run the race, and at the very end, you ask, "Did they cross the finish line?"

  • If Athlete A crosses the line in 2 hours and Athlete B crosses it in 4 hours, the old method says: "Both are winners. They are tied."
  • If Athlete C trips and falls halfway, and Athlete D trips and falls at the very last second, the old method says: "Both are losers. They are tied."

The paper argues that this "Did they finish?" approach is broken. It throws away a huge amount of useful information. It's like grading a student only on whether they turned in their homework, ignoring whether they actually understood the material or how hard they tried. Because so many systems end up with the same "Win" or "Lose" label, it becomes impossible to tell who is actually improving. The authors call this "benchmark saturation"—the test is so blunt that it can't distinguish between good and great anymore.

The New Way (Preference-Based Trajectory Evaluation)
The authors propose a new way to judge these systems. Instead of just looking at the finish line, they watch the entire journey and ask: "Who got closer to the goal faster?"

They use three creative ways to compare the runners:

  1. The "First to the Milestone" Rule (Lexicographic Return): Imagine the race has checkpoints. If Runner A reaches the 10-mile mark in 1 hour and Runner B reaches it in 2 hours, Runner A is better, even if they both eventually finish. This method looks for the first moment where one runner pulls ahead.
  2. The "Cumulative Speed" Rule (Return-Paired Preference): This looks at the whole race. It asks, "At every single point in the race, who was ahead?" If Runner A is slightly ahead for the first half, and Runner B is slightly ahead for the second half, this method calculates the total time advantage. It treats the race as a continuous flow of progress rather than a single yes/no event.
  3. The "Step-by-Step" Rule (Interval-Paired Preference): This focuses on the effort between checkpoints. If Runner A takes a long time to get from mile 1 to 2, but then zooms from 2 to 3, while Runner B is steady but slow the whole way, this method rewards the specific bursts of speed. It asks, "Who was faster to get from one small goal to the next?"

What Happened When They Tried It?
The researchers tested this new method on many different AI "games" and tasks. Here is what they found:

  • Fewer Ties: Under the old "Did they finish?" method, 75% of the time, two different AI systems ended up in a tie. Under the new "Watch the whole journey" method, ties dropped to about 35%. This means the new method can actually tell the difference between systems much more often.
  • More Data Efficiency: Because the new method gets more information out of every single run, you need to run fewer tests to know which AI is better. It's like getting a high-resolution photo instead of a blurry one; you need fewer photos to see the details.
  • Stability: The rankings produced by the new method were more stable. If you removed one test from the results, the old method would sometimes flip the winner, but the new method stayed consistent.

The Big Takeaway
The paper concludes that the reason AI benchmarks seem "stuck" or "saturated" (where no system seems to get better) might not be because the problems are too hard or the data is bad. It might be because the ruler we are using to measure them is too blunt.

By switching from a simple "Win/Lose" score to a detailed "Who got there faster and how?" comparison, we can see real progress again without needing to collect more data or change the AI systems themselves. We just need to look at the journey, not just the destination.

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 →