Fix misleading instruction in shortest_path asking for "length" instead of path (#523)

The prompt asked to "find the length of the shortest path" but the expected
answer is a sequence of directions. This caused models to answer with a number
instead of directions, degrading evaluation results.

Closes #522

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Zafir Stojanovski 2026-03-25 13:02:23 +01:00 committed by GitHub
parent 9a91d92ca6
commit 49b1dbbcce
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 90 additions and 88 deletions

View file

@ -24,7 +24,7 @@ If there is no path from * to #, simply write "infeasible" (without quotes).
Your output should be a sequence of directions that leads from * to #, e.g. right right down down up left
Now, find the length of the shortest path from * to # in the following grid:
Now, find the shortest path from * to # in the following grid:
{grid}
"""