Browse State-of-the-Art › Personalized and Emotional Conversation

Personalized and Emotional Conversation

1 paper with code · 1 benchmark · 1 dataset archive 2025-07-28

Natural Language Processing

Personalized and Emotional Conversation (PEC) is defined as follows: Given the personalized information (P_(R1) and P_(R2)) of two speakers, their conversation context C, the emotion E_K and DA D_K of the response to be generated, and the personalized information P_K of the responder, the goal is to generate an anthropomorphic response Y. Y = argmax_(Y′)P(Y′|C, E_K, D_K, P_K)

Particularly, context C={(U₁,E₁,D₁,P₁),⋯,(U_(K-1),E_(K-1),D_(K-1),P_(K-1))} contains multi-turn conversation content (i.e., utterance Uᵢ), emotion Eᵢ of the associated utterance, DA Dᵢ of the associated utterance, and personalized information Pᵢ of the associated speaker.

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

1 leaderboard table shown for this task, 1 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
CPED (9 rows) GPT-{emo} CPED: A Large-Scale Chinese Personalized and Emotional Dialogue... code — Compare

Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Libraries

Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.

Datasets archive 2025-07-28

1 dataset whose archive record lists this task, ordered by the archive's paper count.

Subtasks archive 2025-07-28

No subtask under this task in the archive's task tree.

Parent tasks archive 2025-07-28

Papers archive 2025-07-28

archive papers tagged: 2 · with a code link: 1 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran: none of the 2 tagged papers has a Syntology run on record

Page 1 of 1: papers 1 to 2 of 2, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.

Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from.

  • 29 May 2022 1 repository listed
    Finally, we provide baseline systems for these tasks and consider the function of speakers' personalities and emotions on conversation.
  • BAPO: Base-Anchored Preference Optimization for Overcoming Forgetting in Large Language Models Personalization
    30 Jun 2024 0 repositories listed
    While learning to align Large Language Models (LLMs) with human preferences has shown remarkable success, aligning these models to meet the diverse user preferences presents further challenges in preserving previous…

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections