- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper introduces PersonaTrust, a benchmark for evaluating trustworthiness of personalized MLLMs. The dataset categorizes user queries into four types (PIQ, EPQ, GPQ, NQ) and tests models under varying levels of evidence availability. Findings show that frontier models frequently fail to abstain or reveal missing context, often hallucinating personalized details instead. To address this, the authors propose PR-Calibrator, a 2-stage wrapper involving query diagnosis and calibration, which significantly improves trustworthiness on complex queries while preserving the model's baseline personalization abilities.
Critical strengths
-
The paper identifies a gap that existing MLLM personalization benchmarks have overlooked: whether personalized assistants remain reliable when user-specific evidence is insufficient or conflicting.
-
The benchmark is well designed, decomposing trustworthy personalization into four question types (PIQ/EPQ/GPQ/NQ) that capture distinct evidence-dependency scenarios.
Critical weaknesses
-
The current evaluation does not sufficiently decouple a model's general personalization capabilities from the specific trustworthiness issues measured by PersonaTrust. Because the benchmark is derived from Persona-MME and LCMP, the authors should report the models' baseline performance on these source datasets. This comparison is necessary to clarify whether the observed failures stem from a specific vulnerability to overstated familiarity, or simply from fundamentally weak personalization skills.
-
The proposed PR-Calibrator introduces a non-marginal computational overhead, which raises practical concerns for real-world serving. Furthermore, the evaluation lacks comparison against more straightforward, lightweight baselines. For instance, the authors should test whether a strong system prompt (e.g., explicitly instructing the model to abstain or provide a disclosed general fallback when context is missing) can mitigate the issue in a single step. Additionally, a simpler two-stage approach can be evaluated, where generation is directly conditioned on the upfront diagnosis step. The necessity of generating an initial draft only to correct it retrospectively in a third stage is not adequately justified.
Questions for authors
-
In Figure 3, GFP is fairly high while FT is low, meaning the models do provide a general response in most cases. Why, then, are P-ACC and A-ACC on GPQ so much lower than GFP? Does a response count as incorrect whenever it fails to explicitly disclose that it is a general fallback, even if the fallback content itself is reasonable?
-
For GPQ, what do the authors think about separately checking whether the model gives a general fallback response versus a (fabricated) personalized response? This would help distinguish “answered generically without disclosure” from “pretended to be personalized.”
-
What is the accuracy of the UPD step itself? How well does it categorize incoming queries into the question types at this stage?
-
The ablation study lacks a description of how the process actually runs when a part of the component is present. For example, in the “+ UPD Step” row, does the pipeline execute only steps 1 and 2 in Figure 5 and stop? If so, where is the diagnosis information injected—into the prompt of the generation step, or elsewhere?
-
Regarding naming: “Never-answerable Questions” does not convey what the category actually tests. A name that reflects the conflict between the query’s premise and the past context might be more intuitive.
5 comments
Response to Reviewer y7UT (2/3)
(Part 2/3)
[W2] (1) PR-Calibrator introduces a non-marginal computational overhead, which raises practical concerns for real-world serving. (2) The evaluation lacks a strong-system-prompt baseline, e.g., one that explicitly instructs the model to abstain or give a disclosed general fallback when context is missing. (3) A simpler two-stage approach, where generation is directly conditioned on the upfront diagnosis, should also be evaluated. (4) The need to generate an initial draft and then correct it in a third stage is not adequately justified.
-
We appreciate this practical concern and acknowledge that PR-Calibrator adds overhead, which is a trade-off for training-free trustworthy personalization. Specifically, diagnosis is independent of the draft to avoid being influenced by an unreliable answer. Meanwhile, preserving the original generation retains the base assistant's personalization pipeline, while PC verifies the draft against the history. Moreover, UPD reads only the query and can run in parallel with generation, with PC following both.
-
We compare a single-call strong-system-prompt baseline with Qwen3.8-27B and PR-Calibrator. The prompt requires grounding user facts in the history, acknowledging missing facts, disclosing general advice, and checking unsupported premises.
The neutral-prompt and PR-Calibrator rows use the reported Table 2 results, and Avg is the macro-average of its eight metrics.
Qwen3.8-27B U-Bench EPQ A-ACC U-Bench GPQ A-ACC U-Bench Avg C-Bench Avg Neutral prompt 23.07 10.31 25.67 31.52 Strong system prompt 46.47 40.83 41.53 35.60 PR-Calibrator 64.07 66.16 50.69 37.69 -
Thank you for this suggestion, and we would like to clarify that this simpler two-stage approach has already been evaluated in Table 3 (the "+ UPD Step" row, see Q4), where the complete PR-Calibrator achieves better overall trustworthiness performance.
-
We agree that this design choice needs a clearer justification. Specifically, we draft first because the two-stage variant improves trustworthiness but halves GPQ F-ACC (), since with the rules in the generation prompt the model turns conservative even when the evidence is present. In contrast, drafting first and calibrating afterwards keeps the original pipeline unchanged (GPQ F-ACC 29.69) and edits only what the history does not support. At the same time, revision without the diagnosis is not enough either, as GPQ A-ACC reaches 15.16, versus 66.16 with it.
[Q1] In Figure 3, GFP is high and FT is low. Why are GPQ P-ACC and A-ACC so much lower than GFP? Is a response counted as incorrect whenever it does not disclose that it is a general fallback, even if the fallback itself is reasonable?
Thank you for this careful question, and your understanding is correct. A reasonable general fallback is still counted as incorrect if the response does not disclose that it is not personalized.
Specifically, GPQ A-ACC counts a response as correct only when it meets all four conditions (Appendix B.2). It does not abstain, it gives a general answer (GFP), it states that the answer is not personalized (FT), and it does not present generic content as personalized. Since both GFP and FT are required, A-ACC cannot exceed the lower of the two, and therefore the low FT caps A-ACC even though GFP is high. GPQ P-ACC additionally requires the response to use at least one available evidence atom and to make no fabricated persona claim.
We count undisclosed fallbacks as failures because the user asked for advice based on their own history. Hence an undisclosed generic answer is read as tailored advice, which is the false sense of familiarity that PersonaTrust targets (Section 3.3). Nevertheless, the fallback itself is still credited by GFP, which is why Figure 3 reports GFP and FT separately.
Response to Reviewer y7UT (3/3)
(Part 3/3)
[Q2] Could GPQ separately check "answered generically without disclosure" versus "pretended to be personalized"?
Thank you, this is a useful distinction, and the judge already records it. Specifically, for GPQ, it returns "gave general answer", "disclosed not personalized", and "fake personalization" separately (Table 5). Based on these records, we split the U-Bench GPQ responses under the None setting into the two cases, where each response is counted once.
| U-Bench GPQ (None) | Answered generically without disclosure | Pretended to be personalized |
|---|---|---|
| GPT-5.6-Sol | 46.4 | 26.3 |
| Qwen3.8-27B | 13.5 | 51.6 |
Thus, the two models fail in different ways. GPT-5.6-Sol mostly answers generically without disclosure, while Qwen3.8-27B mostly presents generic content as personalized. We will add this split for all models in the revision.
[Q3] What is the accuracy of the UPD step itself?
Thank you for the question, which we answer by measuring UPD's classification accuracy on all 1,189 U-Bench and all 493 C-Bench queries with Qwen3.8-27B. Note that UPD sees only the query, so EPQ and NQ cannot be told apart at this stage (Section 4.2), and thus an NQ routed to EPQ counts as correct, because the EPQ calibration request also carries the NQ handbook (Appendix G).
| Subset | PIQ | EPQ | GPQ | NQ ( EPQ) | All |
|---|---|---|---|---|---|
| U-Bench | 94.7 | 95.7 | 72.7 | 95.0 | 89.7 |
| C-Bench | 74.4 | 93.5 | 92.6 | 92.0 | 85.7 |
Thus, UPD diagnoses most queries correctly, with an overall accuracy of 89.7% on U-Bench and 85.7% on C-Bench. The remaining errors concentrate in two cases. On U-Bench, they mostly route recall-style GPQs to EPQ (GPQ accuracy 72.7%). On C-Bench, they mostly route advice-style PIQs to GPQ (PIQ accuracy 74.4%), since query-only diagnosis can mistake generic advice for personal advice.
[Q4] The ablation study does not describe how the pipeline runs when only some components are present. For example, does the "+ UPD Step" row execute only Steps 1 and 2 of Figure 5 and stop, and if so, where is the diagnosis injected?
We apologize for the missing description, and your reading of the "+ UPD Step" row is correct. Specifically, this variant runs Steps 1–2, where the diagnosis (type, needs, premises), the corresponding handbook, and grounding rules G1–G4 are injected into the generation prompt, producing the final response without post-generation calibration. In contrast, the "+ PC Step" variant runs Steps 2–3, where the calibration step receives all handbooks without an upfront diagnosis and determines the appropriate case itself. Thus, both variants require only two model calls. We have clarified how both variants run in Section 5.3 (revised PDF).
[Q5] "Never-answerable Questions" does not convey what the category tests, and a name reflecting the conflict between the premise and the past context may be more intuitive.
Thank you for the suggestion on the name "never-answerable", which we chose to contrast NQ with EPQ and GPQ. Specifically, for those two types, the right response depends on how much evidence is available, while an NQ cannot be answered as posed even with the complete history and has no general fallback (Section 3.1), because its premise conflicts with, or is not supported by, the history. That said, we agree that the name describes the outcome rather than the cause. Therefore, if you find it clearer, we are happy to rename the category in the revision, e.g., to Persona-Conflict Questions (PCQ), which matches the existing PCA-ACC metric.
Response to Reviewer y7UT (1/3)
(Part 1/3)
Thank you for the careful reading and for recognizing that PersonaTrust targets an overlooked gap, whether personalized assistants stay reliable when user evidence is insufficient or conflicting, with a well-designed set of four question types (PIQ/EPQ/GPQ/NQ). We also appreciate the concrete suggestions on baselines, metrics, and naming.
We agree that distinguishing general personalization ability from trustworthiness is important. However, we believe there may be a misunderstanding, as our PersonaTrust benchmark is already designed to disentangle these two aspects.
To complement this analysis, we report performance on the source benchmarks in the table below. To relate these numbers to trustworthiness, the last column first takes the EPQ and GPQ questions that a model answers correctly under Full, and then reports how often the model fails on these same questions under Partial and None.
For PersonaVLM and TAME, source-benchmark results come from their papers, averaged over Persona-MME 32K/128K and LCMP-E/LCMP-H. For Qwen3.8-27B, we evaluate both source benchmarks ourselves.
Thus, Qwen3.8-27B is strong on both source benchmarks, yet on the very questions it answers correctly under Full, 87.7% (U-Bench) and 95.0% (C-Bench) of its Partial and None responses still fail. We will add these results for all models in the revision.