Papers
arxiv:2610.30970

Joint or Per-Option? Compact Encoders for Closed-Set Decisions from 17 Million to 1 Billion Parameters

Published on Oct 22
· Submitted by
Tardelli Stekel
on Oct 27

Abstract

Many language-model pipelines end in a closed-set decision, such as selecting a tool. Prompting a large language model for it is slow and order-sensitive. We ask how small an encoder for such decisions can be and whether it should read the options jointly or separately. In a three-seed study at 32 million parameters, per-option scoring beats joint scoring on a held-out sample of a 37-benchmark decision suite by 5.8 points of chance-corrected skill at matched optimizer steps and by 2.8 at approximately matched training compute; two external benchmarks agree, though not significantly on their unseen tasks. Crossing reader with initialisation shows that the advantage requires a reranker initialisation, whose query-candidate pair input matches per-option reading; from the raw encoder the two readers are indistinguishable. Per-option scoring needs 5 to 13 times more encoder passes: at most twice the median latency, but more than four times the mean. Of six released joint encoders (17 million to 1 billion parameters), the 68- and 150-million-parameter models exceed a 435-million-parameter DeBERTa-v3 zero-shot classifier by 4.9 and 5.9 accuracy points on 209 overlap-audited System1-Arena tasks and are at least on par with it on the 145 tasks unseen in training. The smallest answers a median request in 14 milliseconds on 16 processor threads, against 728 for the classifier. Reordering options changes 12 to 23% of the joint models' answers (per-option scoring: none). Up to 68 million parameters, they lead their size range on a public leaderboard's private, mainly in-distribution tests.

Community

Paper author Paper submitter

Author here. Many LM pipelines end in a closed-set decision: pick a tool, a label, a route. We asked two things: how small an encoder for this can be, and whether it should read the options jointly or one at a time.

  • Per-option vs joint: in a three-seed study at 32M parameters, per-option scoring wins by 5.8 points of chance-corrected skill at matched optimizer steps, and by 2.8 at roughly matched compute. The advantage needs a reranker initialisation; from the raw encoder the two readers are indistinguishable.
  • Cost: per-option needs 5–13× more encoder passes, so joint is what we released.
  • Released models: six open joint encoders, from 17M to 1B. On 209 overlap-audited System1-Arena tasks, the 68M and 150M beat a 435M DeBERTa-v3 zero-shot classifier by 4.9 and 5.9 accuracy points. On the 145 tasks unseen in training they are at least on par with it.
  • Latency: the 17M answers a median request in 14 ms on 16 CPU threads.
  • A caveat we measured: reordering options changes 12–23% of the joint models' answers.

Models: https://huggingface.co/collections/tardellirs/crivo-6acaa1731d71f839970f04a6
Code and results: https://github.com/tardellirs/crivo-decision-encoders

Happy to answer questions!

Sign up or log in to comment

Get this paper in your agent:

hf papers read 2610.30970
Don't have the latest CLI?
curl -LsSf https://hf.co/cli/install.sh | bash

Models citing this paper 8

Browse 8 models citing this paper

Datasets citing this paper 1

Spaces citing this paper 3

Collections including this paper 1