Near-Duplicate Question Detection (WWW 2024)
This entry indexes a publication accepted at WWW 2024 on near-duplicate question detection, available via Amazon Science:
- Source: https://www.amazon.science/publications/near-duplicate-question-detection
- Category: Query Understanding / Information Retrieval
- Type: Industry-linked academic publication (WWW 2024)
- Task: Near-duplicate question detection — identifying questions that are semantically equivalent to ones already asked, a foundational component of community question answering, FAQ/search deduplication, and query understanding pipelines.
- Why it matters: Detecting duplicates lets platforms merge questions, reuse existing answers, reduce content redundancy, and improve retrieval quality downstream.
- Context in the LLM era: The post frames the work against modern IR stacks — dense retrievers, cross-encoder rerankers, retrieval-augmented generation (RAG), and agentic search — where retrieval count and strategy themselves become learnable decisions.
- Honest caveat: This forum entry is a template-style summary. The original abstract, method specifics, datasets, and quantitative results are not reproduced here; the source page and PDF must be consulted for exact claims and numbers.
- Aligned Query Expansion: Efficient Query Expansion for IR (arXiv:2507.11042)
- Beyond the limitation of a single query: training LLMs for query expansion (arXiv:2510.10009)
- Decomposing complex queries for tip-of-the-tongue retrieval (arXiv:2305.15053)
- Few-Shot Generative Conversational Query Rewriting, SIGIR 2020 (DOI: 10.1145/3397271.3401323)
- Hierarchical query classification in e-commerce search, WWW 2024
- Hypothetical Documents or Knowledge Leakage? Rethinking LLM-based query expansion (arXiv:2504.14175)
- Data: PII handling, versioned/de-identified indexes, rollback-capable embedding versions.
- Latency: p99 budgets, cascaded retrieval with early stopping, caching of frequent queries, async reranking.
- Quality: verify offline metric gains (nDCG@10, MRR, Recall@k) translate into online CTR/satisfaction; use interleaving and human audits.
- Safety: whitelist sources, adversarial/poisoning detection, output filtering for open retrieval.
- Cost: token and GPU budget per query, small-model routing, distillation, hybrid sparse+dense retrieval.
Key points
Related topics and cross-references
The post situates this paper alongside related query-understanding work:
Engineering checklist highlights
The post includes a production-readiness checklist applicable to near-duplicate detection systems:
Takeaways for readers
1. Researchers: reproduce baseline comparisons and check for statistical significance and compute-cost reporting. 2. Engineers: treat encoders and rerankers as pluggable modules; evaluate integration cost with existing stacks. 3. Product owners: prioritize user-perceivable benefits (latency, answer trustworthiness, multi-turn consistency) over offline metrics alone.
For the authoritative abstract, method, and experimental results, refer to the official publication page linked above.