What's Hard in English RST Parsing? Predictive Models for Error Analysis

Yang Janet Liu, Tatsuya Aoyama, Amir Zeldes
9/10/2023
cs.CL

No confident code implementation found for this paper.

Abstract

Despite recent advances in Natural Language Processing (NLP), hierarchical discourse parsing in the framework of Rhetorical Structure Theory remains challenging, and our understanding of the reasons for this are as yet limited. In this paper, we examine and model some of the factors associated with parsing difficulties in previous work: the existence of implicit discourse relations, challenges in identifying long-distance relations, out-of-vocabulary items, and more. In order to assess the relative importance of these variables, we also release two annotated English test-sets with explicit correct and distracting discourse markers associated with gold standard RST relations. Our results show that as in shallow discourse parsing, the explicit/implicit distinction plays a role, but that long-distance dependencies are the main challenge, while lack of lexical overlap is less of a problem, at least for in-domain parsing. Our final model is able to predict where errors will occur with an accuracy of 76.3% for the bottom-up parser and 76.6% for the top-down parser.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{liu2023whats,
  title  = {What's Hard in English RST Parsing? Predictive Models for Error Analysis},
  author = {Yang Janet Liu and Tatsuya Aoyama and Amir Zeldes},
  year   = {2023},
  eprint = {2309.04940},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2309.04940v1}
}

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

Discussion