Rethinking Evaluation Metrics for Grammatical Error Correction: Why Use a Different Evaluation Process than Human?

Takumi Goto, Yusuke Sakai, Taro Watanabe
2/13/2025
cs.CL

No official code found. Best implementation: gotutiyan/gec-metrics (14 stars, MIT, last commit 2026-01-25).

Abstract

One of the goals of automatic evaluation metrics in grammatical error correction (GEC) is to rank GEC systems such that it matches human preferences. However, current automatic evaluations are based on procedures that diverge from human evaluation. Specifically, human evaluation derives rankings by aggregating sentence-level relative evaluation results, e.g., pairwise comparisons, using a rating algorithm, whereas automatic evaluation averages sentence-level absolute scores to obtain corpus-level scores, which are then sorted to determine rankings. In this study, we propose an aggregation method for existing automatic evaluation metrics which aligns with human evaluation methods to bridge this gap. We conducted experiments using various metrics, including edit-based metrics, n-gram based metrics, and sentence-level metrics, and show that resolving the gap improves results for the most of metrics on the SEEDA benchmark. We also found that even BERT-based metrics sometimes outperform the metrics of GPT-4. The proposed ranking method is integrated gec-metrics.

View on arXivView PDF

Code Implementations(1)

MIT

A library for evaluation of Grammatical Error Correction (GEC). Accepted to ACL'25 Demo: "gec-metrics: A Unified Library for Grammatical Error Correction Evaluation".

140Shell, PythonSep 24, 20248 months agoMIT

Similar Papers

Cite this paper

@article{goto2025rethinking,
  title  = {Rethinking Evaluation Metrics for Grammatical Error Correction: Why Use a Different Evaluation Process than Human?},
  author = {Takumi Goto and Yusuke Sakai and Taro Watanabe},
  year   = {2025},
  eprint = {2502.09416},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2502.09416v2}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2502.09416.svg)](https://codeofpaper.com/paper/2502.09416)

Discussion