Unverified50% confidenceFactExact time
The evaluation found a real bug: a section named "Trial Threshold Scoring" was buried under the generic "MQL and Lead Scoring," causing the agent to answer 100 instead of 31, and the fix was to add title-matching candidates to the search.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/18/2026
First Seen
Valid until: 1/16/2027
Sources
Related Entities
Related Claims
UnverifiedBy adding to the prompt 'you are seeing part of this database; if you need more information, refuse to answer', schemagate reduced incorrect answers from 16% to 5% in a 100-question pilot.64% similarUnverifiedschemagate achieved an F1 of 0.83 in a 200-question pilot test, and 32 of the 33 false rejections stemmed from a regex bug: the check failed to correctly handle uppercase AS (such as FROM students AS T1), causing aliases to be misread as table names and the query to be rejected.64% similarUnverifiedThe article's data and conclusions all come from a single UP host's demonstration, and certain competitor names in the benchmark tests contain descriptive inaccuracies.63% similarUnverifiedThe first version of retrieval used TOP_K = 12, which stuffed tail noise into the prompt, and the LLM confidently wrote them into the missing-skills list.63% similarUnverifiedThe first-run scorer only accepted lines beginning with `ANSWER:`, causing most answers judged as incorrect to actually be correct—for example, correct responses with the number and label on the same line, Markdown bold formatting, or LaTeX format were all scored 0.61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1057843API
curl https://kongchang.com/api/v1/knowledge/claims/1057843MCP
get_claim(id=1057843)