Skip to content
AI Atlas
PaperActive

Scored vs. Generated Readouts in Behavioral Language Models: An Empirical Study of Elicitation Format

arxiv.org/abs/2609.09882

quality89

Updated 5 h ago · first seen 11 Sept 2026

paper_01M294GKBYD74ZVFP7J7H7RBRA

Published
11 Sept 2026
T1 · 5 h ago
arXiv
2609.09882
T1 · 5 h ago
Category
cs.AI
T1 · 5 h ago

Abstract

Language models fine-tuned on customer behavior can predict outcomes and generate explanations, but these readouts are often treated as interchangeable. Holding model checkpoint and prompt content fixed, we compare probabilities obtained by scoring answer tokens with predictions generated after a written rationale. Across 13 model-domain cells covering four retail tasks in three markets, including two using fully public data and checkpoints, the scored readout ranks outcomes more accurately in 12 of 13 cells (two-sided sign test, p approximately 0.003), by 1.5 to 14.5 points in area under the receiver operating characteristic curve (AUC). Paired bootstrap confidence intervals exclude zero in every newly measured cell. The gap varies with task-specific supervision and mismatch between training and serving formats, ranging from -2.2 points for an untuned base model to +13.7 for rationale-format supervision. Analysis of approximately 9,000 rationales identifies two correlates: reduced reliance on the dominant predictive feature and convergence on stock formulations. Probability saturation does not track the gap. A third readout, eliciting a probability before any verdict, improves calibration (Brier score from 0.47 to 0.15) while ranking within noise of scoring, but only for outcome rates represented in training; it is worse than scoring when the scored head is already calibrated. We interpret these differences through the objectives matched by each readout, identify training choices that narrow the gap, and propose retaining generated rationales while sourcing ranking from the scored head.

Authors 3

Touchapon Kraisingkorn, Krittin Pachtrachai, Wachiravit Modecrua

Specification

Official page

Source:arXiv (Atom API + RSS)T1observed 5 h agohigh

Arxiv announce type
new

Source:arXiv (Atom API + RSS)T1observed 5 h agohigh

arXiv id
2609.09882

Source:arXiv (Atom API + RSS)T1observed 5 h agohigh

Categories
cs.AI

Source:arXiv (Atom API + RSS)T1observed 5 h agohigh

PDF

Source:arXiv (Atom API + RSS)T1observed 5 h agohigh

Primary category
cs.AI

Source:arXiv (Atom API + RSS)T1observed 5 h agohigh

Published
11 Sept 2026

Source:arXiv (Atom API + RSS)T1observed 5 h agohigh

Each value shows its source, tier and observation time. Conflicting claims are kept side by side and flagged — never averaged. How AI Atlas records facts →

Provenance

Attributed facts

9

Source tiers

T19

Freshest observation

5 h ago

Conflicts

None