Inconsistent dialogue responses and how to recover from them

Mian Zhang, Lifeng Jin, Linfeng Song, Haitao Mi, Dong Yu
1/18/2024
cs.CL

No confident code implementation found for this paper.

Abstract

One critical issue for chat systems is to stay consistent about preferences, opinions, beliefs and facts of itself, which has been shown a difficult problem. In this work, we study methods to assess and bolster utterance consistency of chat systems. A dataset is first developed for studying the inconsistencies, where inconsistent dialogue responses, explanations of the inconsistencies, and recovery utterances are authored by annotators. This covers the life span of inconsistencies, namely introduction, understanding, and resolution. Building on this, we introduce a set of tasks centered on dialogue consistency, specifically focused on its detection and resolution. Our experimental findings indicate that our dataset significantly helps the progress in identifying and resolving conversational inconsistencies, and current popular large language models like ChatGPT which are good at resolving inconsistencies however still struggle with detection.

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{zhang2024inconsistent,
  title  = {Inconsistent dialogue responses and how to recover from them},
  author = {Mian Zhang and Lifeng Jin and Linfeng Song and Haitao Mi and Dong Yu},
  year   = {2024},
  eprint = {2401.10353},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2401.10353v1}
}

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

Discussion