Backend
Can Explanations Improve Recommendations? Evidence from Prediction-Informed Explanations
arXiv cs.IR0 views
arXiv:2502.16759v4 Announce Type: replace Abstract: Recommender systems are central to digital platforms, yet they face a fundamental trade-off between accuracy and explainability: Black-box models achieve strong performance but lack interpretability needed for trust and adoption, while existing explainable AI approaches often generate explanations post hoc or sacrifice accuracy. We challenge this view, proposing that explanations, when designed as an integral component of the system and aligned with predictions, can improve \emph{both} interpretability and accuracy. We introduce RecPIE (Recommendation with Prediction-Informed Explanations), a framework that jointly optimizes recommendation predictions and natural-language explanations. RecPIE embeds explanation generation into the learning loop: predictions guide explanation generation (prediction-informed explanations), which are fed back to refine subsequent predictions (explanation-informed predictions) via alternating training. The LLM is fine-tuned using LoRA and reinforcement learning with a usefulness reward derived from recommendation accuracy. We evaluate RecPIE on large-scale point-of-interest recommendation data from Google Maps, where consumer preferences span diverse place categories. RecPIE improves predictive accuracy by 1.7-3.6\% over state-of-the-art baselines and outperforms the strongest full-data baselines using only 25\% of the training data. In human evaluations with 566 participants, RecPIE explanations are preferred 61.5% of the time (versus 16.6% for the best baseline) and rated closer to human-generated explanations. Together, these results suggest that insights about consumer behavior and AI decisions need not be imposed externally or generated post hoc; they can be learned as an integral component \emph{within} the AI systems, allowing systems themselves to discover which insights are useful for improving predictive performance.
Source:https://arxiv.org/abs/2502.16759PreviousFinVeriQA: Financial Research Agents for Question Answering: Routing, Retrieval, MCP Tool Use, and Provenance-Aware Evidence VerificationNextBeyond Dimensionality: Domain Shift and Catastrophic Forgetting in Single- vs. Multi-Vector Retrieval
Related posts

PostgreSQL 19 removes the MultiXact members wall. Reclamation still waits for template0.
0dev.to
Hugging Face Breach: Security Lessons for AI Agents
0dev.to
Incus Project and Migration Trust Boundaries Need Separate Review
0dev.to

Next.js `revalidatePath` vs `revalidateTag` in 2026: Choosing the Right Cache Invalidation Primitive at Scale
0dev.to

'python' Is Not Recognized as an Internal or External Command: Every Fix
0dev.to

Xcode Instruments in Practice: Profiling and Optimizing iOS Apps
0dev.to