← Latest papers
🤖 machine learning

Feedback-to-Rubrics: Can We Learn Expert Criteria from Inline Comments?

This paper proposes and evaluates a method for automatically inferring reusable natural-language rubrics from accumulated inline comments, demonstrating that these distilled criteria can effectively support comment prediction, rubric understanding, and automatic artifact revision in real-world and controlled settings.

Original authors: Kotaro Yoshida, So Kuroki, Yuki Imajuku, Taishi Nakamura, Ryunosuke Iwai, Haruki Goda, Takuya Akiba

Published 2026-05-29
📖 5 min read🧠 Deep dive

Original authors: Kotaro Yoshida, So Kuroki, Yuki Imajuku, Taishi Nakamura, Ryunosuke Iwai, Haruki Goda, Takuya Akiba

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 junior editor at a publishing house. You have a stack of manuscripts, but you don't know exactly what your senior editors are looking for. You've seen their red pen marks (inline comments) on old drafts, but you've never been told the rules behind those marks. You know they circle a sentence and write "Too vague," but you don't know if that means "give more numbers," "explain the logic," or "cite a source."

This paper, titled "Feedback-to-Rubrics," is about teaching a computer to figure out those hidden rules just by looking at the pile of red pen marks.

Here is the breakdown of what they did, using simple analogies:

1. The Problem: The "Tacit" Secret Sauce

Usually, when experts (like senior editors or scientists) review work, they have a mental checklist of what makes something good or bad. But they rarely write this checklist down. It's "tacit" knowledge—like a chef who knows a soup needs more salt but can't explain exactly why or how much without tasting it first.

Large Language Models (LLMs) are great at writing, but they are terrible at guessing these hidden, unwritten rules. If you ask an AI to "make this better," it might change the wrong things because it doesn't know the specific "flavor" of the expert's preferences.

2. The Solution: Turning "Scratches" into a "Recipe"

The authors propose a new way to learn these rules. Instead of asking humans to write a rulebook (which is hard because they don't know how to explain their gut feelings), they look at the inline comments experts have already left on thousands of drafts.

Think of the inline comments as scratches on a map.

  • The Old Way: Try to guess the treasure location by looking at the whole map.
  • This Paper's Way: Look at every single scratch, figure out what kind of treasure the map-maker was hunting for, and then draw a new, clear "Treasure Map" (a Rubric) that explains exactly where to look.

3. How the Machine Learns: The "Guess, Check, and Fix" Loop

The method works like a student studying for a test by doing practice questions and checking the answer key.

  1. The First Guess: The computer looks at a bunch of old drafts and the comments on them. It tries to write a rough "Rulebook" (Rubric) based on what it sees.
  2. The Simulation: The computer then pretends to be an expert. It takes a new draft, reads its own Rulebook, and tries to write comments on it.
  3. The Reality Check: It compares its own comments to the real comments written by the human expert.
    • Did the computer miss a point the human made?
    • Did the computer complain about something the human ignored?
  4. The Fix (The Magic Step): This is the most important part. The computer doesn't just say "I got it wrong." It looks at exactly which rule in its Rulebook caused the mistake.
    • Analogy: Imagine you are trying to learn to bake a cake. You taste it, and it's too salty. Instead of just saying "The cake is bad," you realize, "Ah, the rule I wrote said 'add a pinch of salt,' but I actually needed 'a pinch of salt per cup of flour.'"
    • The computer updates its Rulebook to be more specific, adding boundaries and examples so it doesn't make the same mistake next time.

They do this over and over (iteratively), refining the Rulebook until it perfectly mimics the expert's style.

4. What They Found (The Results)

The authors tested this on nine different types of writing, from research proposals to medical chat logs. They found three main things:

  • Better Comments: When they used the computer's learned Rulebook to generate feedback, the feedback was much more accurate and helpful than when the computer had no rulebook or just looked up similar past comments.
  • A Clearer Rulebook: The final Rulebook wasn't just a list of vague ideas like "be clear." It became a detailed, specific guide (e.g., "If a research question is too broad, point out that it needs a specific scope"). It actually captured the "secret sauce" of the experts.
  • Better Revisions: When they gave this learned Rulebook to an AI and asked it to fix a bad draft, the AI did a much better job of improving the text to match what the human experts wanted.

5. The Bottom Line

This paper shows that you don't need to ask experts to write a manual on how to review things. You can just feed a computer their past notes (comments), let it play "guess the rule" and "fix the mistake" repeatedly, and it will eventually learn a reusable, written set of criteria that captures their expertise.

What they did NOT do:

  • They did not test this on medical diagnoses or clinical treatments.
  • They did not claim this will replace human editors entirely.
  • They did not say this works for any type of data, only for text drafts with inline comments.

In short: They taught a computer to read between the lines of human feedback and turn those messy notes into a clean, usable instruction manual.

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 →