STORYSUMM: Evaluating Faithfulness in Story Summarization

Melanie Subbiah, Faisal Ladhak, Akankshya Mishra, Griffin Adams, Lydia B. Chilton +1 more
7/9/2024
cs.AIcs.CL

No official code found. Best implementation: melaniesubbiah/storysumm (3 stars, MIT, last commit 2026-02-10).

Abstract

Human evaluation has been the gold standard for checking faithfulness in abstractive summarization. However, with a challenging source domain like narrative, multiple annotators can agree a summary is faithful, while missing details that are obvious errors only once pointed out. We therefore introduce a new dataset, STORYSUMM, comprising LLM summaries of short stories with localized faithfulness labels and error explanations. This benchmark is for evaluation methods, testing whether a given method can detect challenging inconsistencies. Using this dataset, we first show that any one human annotation protocol is likely to miss inconsistencies, and we advocate for pursuing a range of methods when establishing ground truth for a summarization dataset. We finally test recent automatic metrics and find that none of them achieve more than 70% balanced accuracy on this task, demonstrating that it is a challenging benchmark for future work in faithfulness evaluation.

View on arXivView PDF

Code Implementations(1)

MIT

Code and data for the paper StorySumm: Evaluating Faithfulness in Story Summarization

30Python, Jupyter NotebookJul 8, 20248 months agoMIT

Similar Papers

Cite this paper

@article{subbiah2024storysumm,
  title  = {STORYSUMM: Evaluating Faithfulness in Story Summarization},
  author = {Melanie Subbiah and Faisal Ladhak and Akankshya Mishra and Griffin Adams and Lydia B. Chilton and Kathleen McKeown},
  year   = {2024},
  eprint = {2407.06501},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2407.06501v3}
}

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/2407.06501.svg)](https://codeofpaper.com/paper/2407.06501)

Discussion