- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper studies whether changing where hidden states are read before generation can improve predictions of whether the model's final answer will be correct. ThinkUQ appends a fixed empty reasoning suffix, reads the hidden state after the boundary, and trains a linear probe to predict correctness. The authors evaluate the method across four Qwen3 scales, multiple tasks, and transfer settings. They also propose a diagnostic that uses source data to assess when the method is applicable.
Critical strengths
The method is simple, and the main experiments provide strong support. Scoring does not require generating reasoning or an answer. In Table 1, compared with Query-end, ThinkUQ improves AUROC by 9.95 and 7.25 percentage points on MMLU subject-OOD testing and MMLU-Pro transfer, respectively. Both methods use matched linear probes, select parameters using only source data, and keep them fixed during transfer. These findings show that changing the readout position before generation can clearly improve correctness prediction. This is a useful empirical contribution.
Critical weaknesses
W1: The additional value of the native reasoning boundary still needs clarification. In §5.3, the main text links the performance gains to computations triggered by the native boundary. The introduction also lists this explanation as a main contribution. Appendix A.2 reports that the full boundary improves AUROC by 0.0124 over the no-tag layout on MMLU-Pro, with a 95% CI of [0.0107, 0.0140]. This supports the transfer value of the tag structure. However, in the B.3 control with 400 source and 200 target examples, user-turn-end and the fixed Answer: prefix also yield point estimates close to those of ThinkUQ when each condition uses its own source-selected probe. These small-sample results do not establish equivalence between the methods, but the additional advantage of the native boundary over other natural positions remains unclear. The main text should therefore distinguish the overall benefit of changing the readout position from the specific contribution of the native boundary.
W2: The proposed source-side diagnostic lacks systematic evaluation. In §6.3, the main text proposes using ThinkUQ when both ranking performance and the separation between correct and incorrect samples improve on source data. The conclusion also presents this diagnostic as a basis for selecting the readout position in practice. However, the paper does not systematically report the choices made using this diagnostic and their corresponding target-domain performance. The prequential codelength results for three configurations in Appendix B.7 provide indirect support, but do not directly evaluate the proposed selection criteria. In particular, for 8B PopQA and 14B GSM8K→MATH, which show negative gains in Table 9, it remains unclear whether the diagnostic would still recommend using ThinkUQ. This limits support for the main text's claim that the source-side diagnostic can guide applicability judgments.
Questions for authors
[Clarification] Can the authors explain, based on A.2 and B.3, what additional advantage the current evidence supports for the native boundary over other natural readout positions? Under which experimental configurations does this conclusion hold?
[Clarification] In the current analysis, how do choices made using only source data and the diagnostic described in §6.3/F.2 correspond to the target-domain results for each configuration in Table 9? In particular, would the diagnostic still recommend ThinkUQ for configurations with negative gains? If no systematic evaluation is available, we suggest framing it as a heuristic supported by preliminary evidence.
3 comments
2. Response to Weakness 2 and Question 2: Systematic Evaluation of the Source-Side Diagnostic
Thank you for highlighting the need to evaluate the diagnostic through its actual choices and target-domain outcomes. We added a systematic evaluation of the same 20 model–task configurations reported in Table 9, covering four Qwen3 scales (1.7B, 4B, 8B, and 14B) and five tasks (TriviaQA, PopQA, GSM8K, MATH, and HumanEval), with ten source splits per configuration.
The source-side rule selects Query-end in most splits for both negative-transfer cases highlighted in the review. It substantially reduces their target-domain losses while retaining positive average gains across all 20 configurations.
1. Turning the source-side principle into an explicit selection rule.
For this supplementary evaluation, we operationalize the principle in §6.3 using source AUROC and standardized correct–incorrect score separation. Probes are fitted on source training data, layers and regularization are selected on source validation data, and the diagnostic is computed on an independent source holdout.
For the probe’s pre-sigmoid score , we define standardized separation as
{\sqrt{(s_{\mathrm{correct}}^2+s_{\mathrm{wrong}}^2)/2}},$$ where $\mu$ and $s^2$ are the score means and sample variances within each correctness class. Larger $D$ indicates a wider correct–incorrect score gap relative to within-class variation. Let $\Delta A$ and $\Delta D$ denote ThinkUQ minus Query-end in source AUROC and separation. **We select ThinkUQ when the paired bootstrap 95% CI lower bounds for both differences exceed zero; otherwise, we select Query-end.** This joint rule requires both improvements. Source bootstrap resampling is stratified by correctness and uses the same sampled examples for both readouts. The selected readout is frozen before target evaluation. Within each split, all strategies reuse the same Query-end and ThinkUQ probes, their target predictions, and the shared correctness labels. Their target results therefore reflect the source-side selection decisions. **2. Target performance across the 20 configurations.** The table reports equally weighted averages across configurations. Utility assigns +1 to a correct answer, −1 to an incorrect answer, and 0 to abstention, and is reported per 100 test questions using source-selected answering thresholds. The AUROC-only selector chooses ThinkUQ when source $\Delta A>0$. Worst changes refer to the most adverse configuration relative to its Query-end baseline. | Selection strategy | Mean target AUROC | Mean utility/100 | Worst ΔAUROC | Worst Δutility/100 | |---|---:|---:|---:|---:| | Always Query-end | 0.6639 | 21.42 | 0 | 0 | | Always ThinkUQ | 0.6784 | 25.50 | −0.1059 | −5.02 | | Source AUROC only | 0.6835 | 22.88 | −0.0589 | −3.22 | | Joint diagnostic, 95% CI | 0.6779 | 23.55 | −0.0117 | −0.28 | The joint diagnostic improves mean target AUROC and utility relative to always using Query-end. Relative to always using ThinkUQ, it reduces the worst observed AUROC loss from 0.1059 to 0.0117, and the worst utility loss from 5.02 to 0.28 points per 100 questions. Its mean utility of 23.55 lies between the two fixed strategies, reflecting the tradeoff between average benefit and controlling adverse transfer. **3. The choices and outcomes for the two highlighted cases.** The table gives selection counts across ten source splits and the resulting target AUROC. The final column reports the change relative to Query-end and its 95% CI. | Configuration | Query-end / ThinkUQ selections | Always Query-end | Always ThinkUQ | Joint diagnostic | Joint − Query-end [95% CI] | |---|---:|---:|---:|---:|---| | 8B PopQA | 8 / 2 | 0.7851 | 0.6793 | 0.7798 | −0.0053 [−0.0178, 0.0000] | | 14B GSM8K→MATH | 6 / 4 | 0.6436 | 0.5822 | 0.6322 | −0.0114 [−0.0275, −0.0007] | For 8B PopQA, the rule selects Query-end in eight of ten splits and reduces the AUROC loss from 0.1059 to 0.0053. For 14B GSM8K→MATH, it selects Query-end in six splits and reduces the loss from 0.0614 to 0.0114; the remaining AUROC change has a 95% CI of [−0.0275, −0.0007]. **These results directly show how source-side choices translate into target-domain outcomes. Across the evaluated configurations, the joint diagnostic substantially reduces adverse transfer while preserving positive average gains in correctness prediction and decision utility.** This supports its use when controlling degradation is a priority. We will specify the rule in §6.3 and Appendix F.2 and add a compact table in Appendix F.2 reporting, for every configuration in Table 9, the number of ThinkUQ selections, the resulting target AUROC, and its change relative to Query-end.Thank you for your clarification. I will maintain my original score.
We sincerely thank you for the thoughtful review and for recognizing the value of pre-generation correctness prediction and our transfer results. Your comments helped us clarify the contribution of the reasoning tags and the choice of readout position.
1. Response to Weakness 1 and Question 1: The Contribution of the Reasoning Boundary
The empty reasoning block improves pre-generation correctness prediction, and its tags add value in the controlled transfer setting. We explain how these findings fit the close
Answer:results and examine how the CoT training format relates to readout performance.1. Changing the readout improves correctness prediction.
In the primary Qwen3-4B MMLU→MMLU-Pro experiment, ThinkUQ improves AUROC from 0.6524 to 0.7249, a gain of 0.0725. Both methods use the same backbone, answer policy, correctness supervision, and probe-fitting procedure.
2. Retaining the reasoning tags provides an additional gain.
The separate Qwen3-4B MMLU→MMLU-Pro experiment in A.2 examines what the tags themselves contribute. It keeps the questions, newline layout, final newline readout, and probe-fitting procedure fixed, and compares:
<think>…</think>blockKeeping the tags improves AUROC by 0.0124, with 95% CI [0.0107, 0.0140].
3. The
Answer:comparison reads after the same reasoning tags.B.3 evaluates Qwen3-4B on 400 MMLU source and 200 MMLU-Pro target examples. Each position receives its own source-selected probe:
Answer:After the question and assistant header, the fixed suffixes are:
ThinkUQ reads the final newline token following
</think>; theAnswer:condition reads the final token of the added prefix. The model has processed the complete empty reasoning block before either readout. All suffix tokens are fixed prefill, and scoring precedes reasoning or answer generation.The
Answer:minus ThinkUQ difference is +0.0120, with paired hierarchical example-bootstrap 95% CI [−0.0406, +0.0621]. User-turn-end also gives a close point estimate in this small panel.We added the same comparison between the two post-block positions on the official DeepSeek-R1-Distill-Llama-8B checkpoint, with its backbone frozen:
Answer:Both paired CIs for the differences include zero. These evaluations consistently show small observed changes when
Answer:is appended after the empty block.4. A training control preserves CoT and removes the reasoning tags.
We further examined how training with reasoning tags relates to the usefulness of the readout. Both training runs start from Qwen3-4B-Instruct-2507 and use rank-16 LoRA and the same 9,984 CoT examples. The new control uses 8,202 steps, matching the step budget of the original 600-minute Tagged-CoT run. Their training sequences are schematically:
The control retains the reasoning content and
Answer:as the delimiter before the final answer, and removes both reasoning tags.At MMLU→MMLU-Pro evaluation, both models are scored before generating reasoning or an answer. The tagged model receives the question and assistant header followed by the empty reasoning block; its probe reads the final newline. The control receives the question and assistant header followed directly by
Answer:; its probe reads the final token of that prefix. Each is compared with its own Query-end baseline:<think>…</think>blockAnswer:aloneThe new control achieves 0.5719 at Query-end and 0.5789 after
Answer:.The experiments support using the empty reasoning block to improve pre-generation correctness prediction: retaining its tags improves transfer, and the model trained with tagged CoT shows a larger gain at this readout. The close
Answer:results are consistent with this benefit, since that prefix follows the same empty block. We choose the final newline after</think>because it follows the chat template and requires a shorter suffix than addingAnswer:. We will revise the introduction and §5.3 to distinguish the overall readout gain from the contribution of the reasoning tags, and add the supplementary results.