Papers › CoSER: Coordinating LLM-Based Persona Simulation of Established Roles
CoSER: Coordinating LLM-Based Persona Simulation of Established Roles
Xintao Wang, Heng Wang, Yifei Zhang, Xinfeng Yuan, Rui Xu, Jen-tse Huang, Siyu Yuan, Haoran Guo, Jiangjie Chen, Wei Wang, Yanghua Xiao, Shuchang Zhou
Role-playing language agents (RPLAs) have emerged as promising applications of large language models (LLMs). However, simulating established characters presents a challenging task for RPLAs, due to the lack of authentic character datasets and nuanced evaluation methods using such data. In this paper, we present CoSER, a collection of a high-quality dataset, open models, and an evaluation protocol towards effective RPLAs of established characters. The CoSER dataset covers 17,966 characters from 771 renowned books. It provides authentic dialogues with real-world intricacies, as well as diverse data types such as conversation setups, character experiences and internal thoughts. Drawing from acting methodology, we introduce given-circumstance acting for training and evaluating role-playing LLMs, where LLMs sequentially portray multiple characters in book scenes. Using our dataset, we develop CoSER 8B and CoSER 70B, i.e., advanced open role-playing LLMs built on LLaMA-3.1 models. Extensive experiments demonstrate the value of the CoSER dataset for RPLA training, evaluation and retrieval. Moreover, CoSER 70B exhibits state-of-the-art performance surpassing or matching GPT-4o on our evaluation and three existing benchmarks, i.e., achieving 75.80% and 93.47% accuracy on the InCharacter and LifeChoice benchmarks respectively.
In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.
Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, on Syntology's MCP service (how to connect):
get_harvested_code_for_paper(arxiv_id="2502.09082")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2502.09082", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2502.09082")
Code
Syntology 23 code samples harvested from 2 repositories linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 4 honoured, 0 violated, 0 with no contract checked; 5 where Syntology's instrument failed) · 14 unverified. Where Syntology's instrument failed: 5 where our contract draft was wrong; failures of Syntology's instrument, not of the code.
By repository: official repository: 1 sample from 1 repository, 1 ran (0 with no instrument failure; 1 where Syntology's instrument failed); community (archive-listed): 22 samples from 1 repository, 8 ran (4 with no instrument failure; 4 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
23 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 4 honoured, 0 violated, 0 with no contract checked; 5 where Syntology's instrument failed) · 14 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.
Licence: 1 of the 23 samples is pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.
Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.
Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.
Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.
A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.
c7933743a582b312 · report
fixture: signature book_name:str/0/str, character:str/0/str, character_profile:str/0/str, background:str/0/str, scenario:str/0/str, motivation:str/0/str, thoughtless:bool/0/bool, other_character_profiles:dict/0/?, exclude_plot_summary:bool/0/bool, fixed_template:bool/0/bool, add_output_example:bool/0/bool, add_rag:bool/0/bool · returned str · level recorded 2026-09-22 4b18614854f76d47 · report
fixture: signature base64_data:str/0/str · returned list · level recorded 2026-09-22 9083059a6053c01a · report
fixture: signature base64_data:str/0/str · returned str · level recorded 2026-09-22 8ac80353df541407 · report
fixture: signature sentences:list/1/str · returned list · level recorded 2026-09-22 6087c37cde8b7d71 · report
fixture: signature text_or_texts:str/0/str · returned list · level recorded 2026-09-22 ccd15a636f8315df · report
fixture: signature text_or_texts:str/0/str, model_name:str/0/str · returned list · level recorded 2026-09-22 a96df6daca0f00a5 · report
fixture: signature data:dict/0/? · returned str · level recorded 2026-09-22 f5012fac79a4d832 · report
fixture: signature text:str/0/str · returned str · level recorded 2026-09-22 e0af9feb46733253 · report
fixture: signature text:str/0/str, dialogue_bra_token:str/0/str, dialogue_ket_token:str/0/str · returned str · level recorded 2026-09-22 ded92e88e0b003ab · report
3886f44e69594927 · report
4a6302a49807a5e7 · report
fb71211b0752f685 · report
d39ee52667a78ef8 · report
338cf403e8136171 · report
1acb7e8163ea94f9 · report
b6444230426a2754 · report
9d6500eb148b11cd · report
936046d800c3e83d · report
cd9ff808f0197b70 · report
0ef004806ceb47bb · report
Method as code Syntology
What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another.
2 assemblies on this paper: 2 harvested, 0 generated, listed in 1 groups (siblings lifted in one batch form one group).
2 sibling assemblies for givencircumstance acting (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.
harvested Assembly for givencircumstance acting (graph method: givencircumstance acting). 22 bricks; individually on a fixture: 8 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 4 honoured, 0 violated, 0 with no contract checked; 4 where Syntology's instrument failed) · 14 unverified. The assembly has not been run end-to-end.
one of 2 siblings
- ChatHaruhi entry · level 0 · unverified ·
72ca06e73065b5f0 - base64_to_float_array helper · level 1 · ran · honoured contract ·
4b18614854f76d47 - cached helper · level 0 · unverified ·
ded92e88e0b003ab - get_bge_embedding helper · level 0 · unverified ·
4a6302a49807a5e7 - get_bge_zh_embedding helper · level 1 · ran · honoured contract ·
6087c37cde8b7d71 - get_db_from_type helper · level 0 · unverified ·
d39ee52667a78ef8 - get_text_from_data helper · level 1 · ran · our draft was wrong ·
a96df6daca0f00a5 - luotuo_openai_embedding helper · level 0 · unverified ·
0ef004806ceb47bb - response_postprocess helper · level 1 · ran · our draft was wrong ·
e0af9feb46733253 - tiktokenizer helper · level 0 · unverified ·
55e9d4ef95279fed - get_bge_embeddings helper · level 1 · ran · honoured contract ·
8ac80353df541407 - get_bge_embeddings_safe helper · level 0 · unverified ·
fb71211b0752f685 - get_general_embedding helper · level 1 · ran · honoured contract ·
ccd15a636f8315df - base64_to_string helper · level 1 · ran · our draft was wrong ·
9083059a6053c01a - get_embedding_for_chinese helper · level 0 · unverified ·
338cf403e8136171 - get_embedding_for_english helper · level 0 · unverified ·
1acb7e8163ea94f9 - get_luotuo_model helper · level 0 · unverified ·
936046d800c3e83d - is_chinese_or_english helper · level 1 · ran · our draft was wrong ·
f5012fac79a4d832 - get_general_embeddings helper · level 0 · unverified ·
b6444230426a2754 - get_general_embeddings_safe helper · level 0 · unverified ·
9d6500eb148b11cd - luotuo_embedding helper · level 0 · unverified ·
cd9ff808f0197b70 - download_models helper · level 0 · unverified ·
3886f44e69594927
harvested Assembly for givencircumstance acting (graph method: givencircumstance acting). 1 brick; individually on a fixture: 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.
one of 2 siblings
- get_character_prompt entry · level 1 · ran · our draft was wrong ·
c7933743a582b312
Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2502.09082") returns these assemblies with each brick's role and wiring (how to connect).
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
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