Unverified50% confidenceFactExact time
The default logic of most RAG evaluation tools is any-hit: as long as any document labeled as relevant appears in the Top-K results, it counts as a hit.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/16/2026
First Seen
Valid until: 1/14/2027
Sources
Related Entities
Related Claims
UnverifiedThe recommended troubleshooting sequence for RAG systems is: first build a test set with ground-truth answers, check whether the retrieved chunks contain the answer for failed cases, and if retrieval is correct but generation fails, prioritize adjusting the prompt and context ordering before upgrading the model.63% similarUnverifiedA RAG system should maintain a small regression test set (golden dataset) containing real questions and known answers, and run it every time the chunking strategy, embedding model, or prompt is modified, in order to catch regressions before launch.63% similarUnverifiedIn deployment decisions, all-evidence should serve as the primary reference metric, because it is closer to the user's actual experience; any-hit can be retained as a diagnostic tool.62% similarUnverifiedA common practice for achieving idempotency is to assign a globally unique idempotency key to each message or task, with the receiver checking whether the key has already been processed before handling it.62% similarUnverifiedPerforming deterministic validation on tool-call payloads (precisely checking parameters such as date, timezone, account, and duration) is preferable to having another LLM judge whether the result is reasonable, because deterministic validation has a zero false-positive rate.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1048177API
curl https://kongchang.com/api/v1/knowledge/claims/1048177MCP
get_claim(id=1048177)