Unverified50% confidenceSolutionExact time
Quantity assertions based on business semantics (such as validating the number of chapters) often catch truncation issues better than pure JSON format validation.
1
Sources
50%
Confidence
Long-term
Relevance
10/12/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedConverting tables to Markdown or structured JSON before chunking yields significantly higher retrieval accuracy than directly flattening and concatenating, because the semantic relationships between rows and columns are preserved.70% similarUnverified工具调用的可靠性高度依赖模型输出严格遵循预定义的 JSON Schema，任何字段类型偏差、缺失或多余都可能导致框架层的解析失败65% similarUnverifiedIn the scoring bug, the original strict comparison often equated an application's inability to parse directly with an incorrect model answer — for example, JSON wrapped in a Markdown code fence would be rejected by the JSON parser even if the values were correct.64% similarUnverifiedOnce final JSON parsing fails, subsequent semantic checks are skipped entirely, which is the technical root cause of the 'task completed yet zero score' phenomenon.64% similarUnverifiedThe value of a component is highly dependent on the task type and data distribution; general retrieval augmentation patterns do not necessarily apply to multi-hop question-answering scenarios.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1003925API
curl https://kongchang.com/api/v1/knowledge/claims/1003925MCP
get_claim(id=1003925)