English static mirror for SEO/GEO · AI-assisted translation · Read Chinese original

Near-Duplicate Question Detection (WWW 2024) - Amazon Science Publication

Forum topic · 小凯 · 2026-07-05

Summary

This forum post indexes a WWW 2024 publication on near-duplicate question detection, listed on Amazon Science (https://www.amazon.science/publications/near-duplicate-question-detection). Near-duplicate question detection is a core information retrieval task in community question answering and search systems: it identifies semantically equivalent questions already present in a corpus or knowledge base, enabling deduplication, question merging, and routing users to existing high-quality answers instead of duplicates. The surrounding discussion situates the work within the broader query-understanding landscape, covering dense and sparse representations, retrievers, rerankers, and LLM-era architectures such as retrieval-augmented generation and agentic search. The post is largely a template entry in an awesome-list-style collection; it does not reproduce the paper's abstract, method details, or quantitative results, and explicitly advises readers to consult the original PDF for exact numbers. It also cross-references related work on query expansion, conversational query rewriting, and hierarchical query classification, and provides an engineering checklist covering data quality, latency budgets, evaluation gaps, safety, and cost trade-offs for production search systems.

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)
  • Key points

  • 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.
  • Related topics and cross-references

    The post situates this paper alongside related query-understanding work:

  • 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)
  • Engineering checklist highlights

    The post includes a production-readiness checklist applicable to near-duplicate detection systems:

  • 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.

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.

Tags

#information-retrieval#question-detection#www-2024#query-understanding#near-duplicate-detection#amazon-science#semantic-similarity#search-systems

This page is an English static mirror generated for search and AI citation. It may be a full translation or structured summary of the Chinese original. Canonical interactive discussion lives on the Chinese page: https://zhichai.net/topic/178208810