Large language models (LLMs) increasingly store user preferences in persistent memory to support personalization across interactions. However, in third-party communication settings governed by social and institutional norms, some user preferences may be inappropriate to apply. We introduce BenchPreS, which evaluates whether memory-based user preferences are appropriately applied or suppressed across communication contexts. Using two complementary metrics, Misapplication Rate (MR) and Appropriate Application Rate (AAR), we find even frontier LLMs struggle to apply preferences in a context-sensitive manner. Models with stronger preference adherence exhibit higher rates of over-application, and neither reasoning capability nor prompt-based defenses fully resolve this issue. These results suggest current LLMs treat personalized preferences as globally enforceable rules rather than as context-dependent normative signals.
Figures & tables
Figure 1: Preference selectivity across models. Lower Misapplication Rate (MR) and higher Appropriate Application Rate (AAR) indicate stronger selectivity, with the ideal point at (0, 100). Many models lie near the dashed line (y = x), indicating limited selectivity.
Figure 2: BenchPreS setup overview. Given a task prompt and persistent memory containing user preferences, the model must generate responses that apply contextually appropriate preferences while suppressing inappropriate ones. The top example succeeds, whereas the bottom example fails.
Model
MR ↓
AAR ↑
AAR - MR ↑
Gemini 3 Pro
86.48% ± 0.72
88.69% ± 0.58
2.21
DeepSeek V3.2
61.15% ± 1.14
87.63% ± 1.26
26.48
Claude-4.5 Sonnet
52.99% ± 1.37
87.93% ± 0.81
34.94
GPT-5.2
40.95% ± 2.54
87.33% ± 0.34
46.38
Qwen3 235B A22B Thinking 2507
84.62% ± 1.06
82.85% ± 1.44
-1.77
gpt-oss-120b
74.28% ± 0.63
87.40% ± 0.89
13.12
Table 1: Quantitative Results across 10 widely used LLMs. Misapplication Rate (MR), Appropriate Application Rate (AAR), and their difference (AAR - MR). Asterisk (*) indicates non-reasoning models. Models are separated by size using 500B parameters as the cutoff. Bold indicates best-performing model for each metric.
Figure 3: Qualitative Failure Cases. Examples where models apply user preferences that should be suppressed. Segments highlighted in red denote preference reflections that are normatively inappropriate for the given context.
Figure 4: Performance comparison of non-reasoning and reasoning-enabled model variants in terms of Misapplication Rate (MR), Appropriate Application Rate (AAR), and IFBench score.
Model
Prompt Strategy
MR ↓
AAR ↑
Gemini 3 Pro
Default
86.48%
88.69%
Mitigation
12.80% (-73.68 pp)
84.87% (-3.82 pp)
DeepSeek V3.2
Default
61.15%
87.63%
Mitigation
40.68% (-20.47 pp)
84.84% (-2.79 pp)
Claude-4.5 Sonnet
Default
52.99%
87.93%
Mitigation
14.04% (-38.95 pp)
84.75% (-3.18 pp)
Table 2: Effect of selectivity-oriented prompting on Misapplication Rate (MR) and Appropriate Application Rate (AAR). Values in parentheses denote percentage-point (pp) changes relative to the default setting.
Figure 5: Effect of selectivity-oriented prompting on MR and AAR for Qwen3 235B A22B 2507. Hatched regions indicate changes from the default setting.
Figure 6: Performance comparison across five communication domains. Results are reported for Gemini 3 Pro, GPT-5.2, Claude-4.5 Sonnet, K-EXAONE-236B-A23B, and Llama-3.3 70B Instruct.
Task Completeness (1–5)
Preference Selectivity
Model
Without Preferences ↑
With Preferences ↑
AAR − MR ↑
Gemini 3 Pro
4.855
3.746 (-1.109)
2.21
DeepSeek V3.2
4.734
4.734 (0.000)
26.48
Claude-4.5 Sonnet
4.637
4.183 (-0.454)
34.94
GPT-5.2
4.925
4.957 (+0.032)
46.38
Table 3: Task completeness with and without preferences stored in persistent memory. Scores are measured on a 1–5 scale. Parentheses in the With Preferences column denote the difference relative to Without Preferences .
Figure 7: Misapplication Rate (MR) across preference categories. Results are reported for GPT-5.2, Claude-4.5 Sonnet, DeepSeek V3.2, Qwen3 235B A22B Thinking 2507, and Gemini 3 Pro.
Figure 8: Example of reasoning for selective preference regulation. The reasoning trace shows how the model evaluates preferences under the given communication context and suppresses those that conflict with the task. Segments highlighted in red indicate the model’s justification for excluding inappropriate preferences.
Benchmark
Focus
Persistent-memory
Application
Suppression
LaMP ( Salemi et al., 2024 )
Profile-based personalization
×
✓
×
PrefEval ( Zhao et al., 2025 )
Multi-session preference application
×
✓
×
RoleLLM ( Wang et al., 2024 )
Persona consistency
×
✓
×
FollowBench ( Jiang et al., 2024 )
Instruction constraint compliance
×
✓
×
BenchPreS
Preference selectivity
✓
✓
✓
Table 4: BenchPreS differs from prior benchmarks by evaluating whether persistent-memory LLMs can both apply appropriate preferences and suppress inappropriate ones under the current communication context.
Appendix figures & tables8 assets
Supplementary material from the paper’s appendix.
Appendix
Value
Profiles
10
Attributes/Profile
152
Contexts/Profile
39
Preferences ( g=1 )/Context
1.7
Preferences ( g=0 )/Context
3.3
Appendix
Table 5: Summary statistics of BenchPreS.
Evaluator Pair
Agreement
Cohen’s κ
DeepSeek-R1 vs GPT-5-mini
92.67%
0.853
DeepSeek-R1 vs Human
88.67%
0.773
GPT-5-mini vs Human
84.00%
0.680
Appendix
Table 6: Judge validation on 300 sampled instances.
Figure 9: Example of reasoning for a failure case where inappropriate preferences are applied. Bold text highlights instances where the model treats inappropriate preferences as instructions to be followed.
Recipient
Task
Public Domain
Bank Loan Officer
Apply for personal loan
finance
Credit Union Representative
Consolidate debt
Financial Advisor
Plan investment portfolio
Mortgage Broker
Refinance existing mortgage
IRS Agent
Resolve tax discrepancy
Defense Attorney
Prepare case strategy
Appendix
Table 7: List of recipient–task pairs grouped by formal communication domain.
Figure 10: Prompt Template for Task Solving.
Figure 11: Prompt-Based Defense Template for Task Solving.
Figure 12: Prompt Template for LLM-as-Judge Evaluation.
Figure 13: Prompt Template for Evaluating Task Completeness.