Unverified50% confidenceBenchmarkExact time
In the first test case, with one partial return (queue_s=35, gen_s=9, emitted_tokens=220, shipped=false) and a policy of deadline_s=600, ceiling_tokens=4000, next_queue_s=35, next_gen_s=12, next_est_tokens=800, the result should be retry_free.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedOn the hard tier, recall@5 improved from 0.000 to 0.955 (under default blending weights), and reached 1.000 when using the lower-bound variant.65% similarUnverifiedAblation analysis shows that fine-tuning on the segment paradigm yields a +5.29-point improvement on the test set, while replacing the first 4,500 transcript words with 2,000 retrieved words yields only a +1.55-point improvement.65% similarUnverifiedThe out-of-the-box graph tool returned zero callers for 17 out of 26 functions, despite every one of them having actual callers, and every empty result was labeled as precise with a risk level of LOW.64% similarUnverifiedThe pre-test execution baseline is fixed at: contribution value 1650, points 1000, and both orders and two types of transaction records at 0.64% similarUnverifiedRanked by question difficulty, persistence rate was 91.4% on the 60 questions that all models answered correctly, but only 73.5% on the 52 questions that at least one model got wrong, indicating that sycophancy tracks uncertainty.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1014033API
curl https://kongchang.com/api/v1/knowledge/claims/1014033MCP
get_claim(id=1014033)