Unverified50% confidenceTradeoffExact time
In RAG scenarios, Recall is usually prioritized over Precision, because missing a piece of key evidence often directly leads to an incorrect answer, whereas retrieving a few extra irrelevant documents only increases context noise and token cost.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIn standard vector databases and RAG solutions, conflicting facts are silently overwritten, causing decision history to disappear with zero provenance.74% similarUnverifiedIn the medical field, models often lack reliable memory of the latest guidelines, hospital regulations, and drug package inserts, and direct generation is prone to hallucinations; retrieving authoritative corpora via RAG and attaching sources both improves answer accuracy and provides a basis for subsequent manual verification.73% similarUnverifiedIf incorrect information is saved to long-term memory, it will contaminate subsequent tasks; only truly valuable, confirmed information should be saved.70% similarUnverifiedFine-tuning is highly inefficient at injecting factual knowledge and is better at adjusting behavioral patterns than memorizing specific facts, so knowledge gaps are more efficiently addressed with RAG.70% similarUnverifiedIn retrieval evaluation, Recall@k is prioritized, because missing evidence leaves downstream generation with no way to recover, whereas bringing back a small amount of noisy documents can usually still be filtered out by the context window or a reranker.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1015435API
curl https://kongchang.com/api/v1/knowledge/claims/1015435MCP
get_claim(id=1015435)