Query-complexity classification estimates whether a query needs high- or low-complexity reasoning so inference budget can be adjusted per request. section 15.2 section 15.5
It appears inside AutoThink as one part of efficient reasoning, alongside steering-vector guidance. The classifier is trained during preprocessing and then used at inference to choose token budget transparently. section 15.2 section 15.5
In this workflow, it is tied to:
- preprocessing on query-response pairs and calibration data. section 15.2
- inference-time budget selection before decoding begins. section 15.2
- reasoning-path steering through control vectors. section 15.2
AutoThink evaluation setup
A local Qwen 2.5 0.5B Instruct model is evaluated on OptiLLMBench GSM8K samples while AutoThink automatically applies the pretrained classifier during decoding. section 15.2 section 15.5
