TimeRoute: Time-Aware Modality Routing and Diffusion for Multi-Modal Recommendation

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2608.10983v2 Announce Type: replace-cross Abstract: Multi-modal recommenders fuse user-item interaction signals with item modalities such as text, images, and audio, but the usefulness of each drifts over time and at different rates. For example, around Valentine's Day, chocolate purchases become less driven by textual ingredient cues and more by visual packaging and ambient audio. This \emph{modality time-scale mismatch} gives rise to two coupled challenges: (1) users with different temporal behavior profiles require different modality proportions, and (2) less relevant modalities are more likely to introduce outdated or misleading signals into the recommender. We address both challenges within a unified diffusion-based recommender, \textbf{TimeRoute}. A temporal-aware modal router maps each user's aggregated temporal profile to a personalized modality distribution, replacing the globally shared fusion weights used in prior work. The diffusion-based graph reconstructor is conditioned on the same profile through Feature-wise Linear Modulation (FiLM) with dual-stream long- and short-term denoising heads. This design captures both slowly and rapidly evolving temporal dynamics to suppress outdated modality edges before they enter the propagation graph. Experiments on TikTok, Amazon-Baby, and Amazon-Sports, averaged over 10 seeds, demonstrate consistent improvements over strong baselines across Recall@K, Precision@K, and NDCG@K, reaching up to 9.8\% (P@20 on Amazon-Baby). Controlled attribution studies further show that these gains require both the proposed mechanisms …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2608.10983
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.