Outside the Radius: Reject Unsupported Requests Before You Route Them
TL;DR for operators Before routing a user request, an automated service must first decide whether the request belongs to any capability it supports. A classifier forced to choose among known intents cannot answer that question reliably through low confidence alone. Xu, Kang, and Lü separate rejection from classification.1 Their gate represents each supported intent with several local acceptance regions because valid requests may form distinct semantic groups. It rejects a request when the request falls outside every region, after comparing each distance with that region’s learned acceptance radius. The method reports the highest out-of-scope F1 in all nine comparisons spanning three datasets and three known-intent ratios. ...