This COLING 2025 paper proposes Persona-DB, a retrieval-based personalization system that transforms user profiles and histories into a hierarchy of History, Distilled Persona, Induced Persona, and Cache; it embeds these representations to match similar users, retrieves information from the current and neighboring users, and asks GPT-3.5-turbo-0613 to predict a response. Persona here is not psychometric personality: it consists of LLM-generated summaries and inferences about values, ideology, interests, roles, opinions, and behavioral patterns. The paper evaluates two tasks. RFPN contains 13.3k responses from 8.4k users to 3.8k Twitter headlines and predicts sentiment polarity and intensity. OpinionQA predicts individual Pew survey responses for Biomedical and Food Issues, 67 questions and 2,537 respondents, Global Attitudes, 104/2,596, and America in 2050-90/2,524, with 1,000 test cases per topic. At RFPN top-40, Persona-DB reports 47.67 Spearman, 47.88 Pearson, 62.66 Micro-F1, and 50.59 Macro-F1, versus 44.89/45.05/59.96/47.32 for IntSum and 42.80/43.09/59.58/48.80 for History Full. For the 100 sparsest nonempty-history users, 13.81 interactions on average, it obtains 56.75 Pearson versus 45.41 for IntSum, a difference of 11.34 points that the paper describes as 11%. For the 300 most frequent users it reaches 49.71 versus 46.58. Efficiency evidence narrows as capacity falls: at top-10, Persona-DB exceeds IntSum by only 0.13 Pearson points and 0.20 accuracy points. Table 3 compares methods at equal top-k values of 40, 30, and 10 and does not itself establish the introduction's ten-times-smaller maximal retrieval claim. It also does not measure total cost, because hierarchical construction requires prior LLM and embedding calls. Figure 3 places Persona-DB above baselines on OpinionQA, but provides bars without exact values, errors, or outputs. Human validation scores 50 extractions using three graduate students and reports a 3.9/5 mean, without inter-rater agreement, dispersion, or a sufficiently reported rubric. Code audit materially changes the main interpretation. get_user_profile2 excludes the target question from the current user's history, but UserRetriever.get_user_analysis with nb_hist_only=True includes every neighboring question-answer pair, the source comment explicitly says it includes the current query. join_db concatenates these records before retrieval into the prompt. In OpinionQA, where many respondents answer the same survey questions, collaborative context can therefore contain neighbors' answers to the exact target item. Without rerunning evaluation after excluding post_id from every neighboring database, the reported gain cannot distinguish persona generalization from same-item collaborative filtering and label leakage. History Full is not literally complete either: both runners remove records until histories fit 2,000-2,500 tokens. The release has no tests, CI, Persona-DB data, README-referenced data.txt, derived personas, embeddings, executed prompts, predictions, or results; RFPN requires reconstructing tweets from pointers through an old API workflow, and OpinionQA preparation code is absent. Source compiles syntactically but uses a legacy environment, broad dependencies, unbounded retries, and no repository-wide license. The paper supplies point estimates from one run at temperature 1 without intervals, tests, replications, or bootstrap. The defensible conclusion is narrow: hierarchical profile abstractions and collaborative retrieval may improve response prediction on these datasets, especially with larger retrieval capacity and sparse users, but the study does not validate personality, profile fidelity, unseen-user or unseen-question generalization, or operational efficiency. Potential target-question leakage prevents clean attribution of OpinionQA results to the persona mechanism.
Research question
Can a hierarchical base of profiles and histories, enriched with data retrieved from similar users, maintain or improve the prediction of personal responses using fewer context elements than conventional histories, recency, or summaries?