- Rating
- 2
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
The paper proposes SE-OPSD, a reference-free on-policy self-distillation method for open-ended QA. It introduces Self-Elicited Privileged Context (SEPC), which captures query-specific response requirements through five structured views and guides a privileged teacher during distillation. The student is trained to incorporate this guidance into direct-answer generation without requiring SEPC at inference time. Experiments on HealthBench and WildBench show consistent improvements over base models and reference-based baselines.
Critical strengths
- The paper extends on-policy self-distillation to open-ended QA, where reliable reference answers or verifiable rewards are difficult to obtain. The proposed approach achieves consistent improvements across multiple models and benchmarks without relying on external teachers.
Critical weaknesses
- The paper provides limited insight into why this works, when it is effective, or what fundamentally distinguishes it from existing context-distillation methods. Test-time SEPC already achieves better performance, raising questions about the necessity of additional training. The comparison is also somewhat limited, as simpler alternatives, such as generating all five SEPC views in a single call or combining planning and answer generation in one pass, are not explored. Furthermore, the efficiency analysis focuses on inference token counts without accounting for training costs or measuring actual wall-clock latency. Given the relatively short generated responses and the possibility of parallelizing SEPC elicitation, the practical latency benefits may be less significant. Overall, it remains unclear whether the efficiency gains are substantial enough to justify the additional training effort.
Questions for authors
-
How does SE-OPSD compare to a test-time baseline that generates all five SEPC views in a single call (or a single-pass approach that combines SEPC elicitation and answer generation), in terms of performance and inference latency?
-
How much training compute does SE-OPSD require, and how many inference requests are needed to offset this cost?
-
Is there evidence that SE-OPSD learns query-specific response-framing decisions, rather than simply adopting general response patterns?