Generative4.10
XJTLUUniversity of LiverpoolPolyU
Generative recommenders emit item-ID tokens left to right, so temporary diversity at inference can only rewrite one position mid-decode and often produces IDs that do not exist in the catalog. ReGen uses a bidirectional Transformer to predict all 4 ID tokens…
Personalization4.75
Alibaba
Taobao search CTR models mainly remember historical clicks through item IDs, so the same item with a different main image is almost indistinguishable to the model. FineSID turns each item image into 30 discrete codes across four VAR tokenizer scales from 1×1…
Personalization4.05
USTC
Generative recommenders use beam search to emit item-ID tokens one by one, and tail items have low generation probability and are often pruned in the first one or two steps: on Amazon Industrial & Scientific, MiniOneRec's 50 candidates cover only 11.94% of…
Personalization4.10
Duke UniversityGeorge Washington University
Personalized reward models score replies per user, but each user labels only a few dozen preference pairs, so most unlabeled replies go unused. Pairwise loss only constrains the score gap under the same prompt, so scores from different prompts can shift as a…
Personalization4.10
Renmin University of China
When a sequential recommender encodes each historical behavior, some behaviors converge after one layer while others need several stacked layers to stabilize. In a three-layer SASRec, 76.1% of behaviors are stable after the first layer and 6.7% need the…
AI Search4.65
Perplexity
Perplexity releases 0.6B and 9B multi-vector retrievers that encode text, images, and document screenshots: each document token stores a 128-d vector, and scoring sums MaxSim of each query vector against document vectors. Both models distill token-by-token…
AI Search4.40
TsinghuaRenmin University
When rewriting a query vector with first-round retrieved documents or an LLM-written hypothetical answer (HyDE), the usual approach averages feedback vectors and interpolates with the original query. DIFF argues that each piece of feedback only supports…
Agentic4.40
KAISTKorea University
Korea University and KAIST have Claude Code (Claude Opus 5.5) design retrieval tools for a search agent: it reads each question's execution log and score, jointly edits pre-generated index files, executable search scripts, and usage instructions, and after 10…
Agentic4.40
Northeastern UniversityTsinghua
Northeastern University and Tsinghua find that in retrieve-while-reasoning RAG, later sub-queries keep drifting away from the original question along the direction earlier sub-queries already moved, and the effect grows with step count. MAPS therefore makes…
Agentic4.40
Parlant
Parlant used to ask an LLM whether each customer-service rule is relevant every turn—about 69,000 tokens for 36 rules. S&Q instead has an LLM offline write 10 triggering user messages and 10 easily confused counterexamples per rule and trains a logistic…
Agentic4.30
IBM
IBM builds ClariEdge, a ~3,900-sample multi-turn RAG clarification set that specially includes hard negatives that "look ambiguous but the referent is already fixed by context," then LoRA-tunes small Granite models to decide whether to clarify and to list…
Infra4.35
An independent researcher compares "add 2:4 sparsity" versus "drop one precision tier" on Llama-3.1-8B-Instruct and Qwen3-8B under matched storage bits (including sparse indices) and matched nominal compute tiers, with measurements on L40S, H100, and RTX PRO…
Infra4.25
SGLangAMDNVIDIA
SGLang, NVIDIA, and AMD use a plugin framework to plug specialized fused kernels into SGLang, cutting inter-kernel waits and cross-GPU communication at low concurrency. On AgentX replays of DeepSeek-V4.1-Flash + DSpark, per-user P90 generation rises from…
Infra4.10
Hisense's RCSD continues training a speculative-decoding draft model that was distilled with HASS, using DPO or GRPO: sequences from the target alone are "good," sequences alternating target and draft are "bad," and the GRPO variant scores by acceptance rate.…
Infra4.10
Scitix.AI's UlaCache maps every GPU KV pool and CPU memory into one logical address space so GPU and CPU each store different history, and removes MLA's cross-GPU duplication under TP; the GPU pool is shared across requests with a bucketed parallel LRU for…