JevK5 v0.3 (4B) and JevK5-9B: please run both (declared overlap inside)

#19
by alibiserikbay - opened

Update (2026-09-25): the 9B row now points to JevK5-9B v0.3.3, trained for 1.5 epochs on the same data (details in the comment below). The 9B numbers under "What we measured ourselves" are v0.3's. The optional JevK5-Lite row is also in a comment below.

Hi! Thanks again for the lift run in #13. We released JevK5 v0.3, and a 9B trained on the same data. Could you run both?

What to run

Row Weights Temperature GPU memory (bf16)
JevK5 v0.3 (4B) alibiserikbay/JevK5 @ c4f7fdb3aeab5582336406e78d3bef11bf98833d (Hub tag v0.3) 1.22 (>16 options: 0.93) ~9 GB
JevK5-9B v0.3.3 (updated from v0.3) alibiserikbay/JevK5-9B @ d6521a18a86999190e9d775c915af3d6d6772fc4 (Hub tag v0.3.3) 1.316 (>16 options: 1.05) ~19 GB
  • Same runtime and readout as the 0.2.2 run: pip install "jevk5 @ git+https://github.com/allebee/jevk5@v0.3.0", then JevK5("alibiserikbay/JevK5").probabilities(state, question), or JevK5("alibiserikbay/JevK5-9B"). Questions with more than 16 options take the same knockout path as in #13, so the lifted adapter should work unchanged. The one runtime change in 0.3.0: each repo's jevk5_config.json now also carries its own second temperature for more than 16 options (knockout_temperature), so please use 0.3.0, not 0.2.2. Without the key (v0.2) nothing changes.
  • The v0.3 4B replaces v0.2 at the same repo. v0.2 stays at the Hub tag v0.2, so by your superseded policy the 4B row would move to v0.3. The 9B is a new row.
  • Cost: the 9B takes about 2-3x the 4B's time per pass. On JevBench's short items on an H100, p50 is 31 ms against 13.6 ms (the 9B measured while another job shared the GPU).

Declared overlap (both models, same training data)

  • Test or validation items in training: none that we know of. Every public and teacher-written training row was checked against the test and validation text of 35 index benchmarks and JevBench's public items. A row was dropped for an exact match (after normalizing) or for any shared 8-word sequence. On 2026-09-25 we re-checked the final training set for exact question matches against ARC, MMLU, OpenBookQA, CommonsenseQA, HellaSwag, WinoGrande and GSM8K test and validation, and found none. That includes the 15 ARC test rows your notes find duplicated in ARC train. GPQA and HLE are gated and were not checked; no source is built from them.
  • No MMLU, MMLU-Pro or BBH at all, in any split. The 980 MMLU-Pro test ids that v0.1/v0.2 trained on are not in v0.3. MMLU's auxiliary_train was dropped too (it is mostly RACE, which is for non-commercial research only).
  • Other splits of the same dataset in training (rows in training; train splits, deduplicated against your test and validation items):
    • 26/27 ARC-Easy/Challenge: train, 1,186
    • 51 OpenBookQA: train, 791
    • 52 CommonsenseQA: train, 1,186
    • 30 GSM8K: train, 2,373
    • 28 WinoGrande: winogrande_xl train, 2,373
    • 29 HellaSwag: train, 2,373
    • 4 BANKING77: train, 791 (each shown with at most 16 intents)
    • 5 CLINC150+OOS: plus train, 1,186 (at most 16 intents each)
    • 10 SGD: train (30 of 127 files), 1,186
    • 37 Amazon ESCI: train (3 of 11 shards), 1,186
    • 62 When2Call: train_pref, 1,978
    • 40 iSarcasmEval: train.En, 1,581
    • 59 RAGTruth: train, 1,186
    • 61 HoVer: train claims with their cited Wikipedia introductions, 1,582
    • 64 New Yorker matching: fold 0 train, 791
  • Teacher-written questions:
    • 53 of the 3,270 Qwen3.6-27B questions (the same ones v0.2 trained on) share at least one 8-word sequence with 11 ContractNLI (41) or 10 SGD (12) test/dev text. They were reported and kept.
    • GPT-6 Luna questions with any hit were dropped: 40 ContractNLI, 6 SGD, 3 ARC, 3 ToolRet and 2 RAGTruth.
  • Not in training: ANLI and NLI4CT. Their train splits were used only in an unreleased development variant.
  • Selection used held-out teacher questions, a hand-written set, and held-out rows of the train splits above. No index test item was used. Our many-options checks (BANKING77, CLINC150, MASSIVE) use train-split items only, and none of those items is in the training data.

What we measured ourselves (for context, not index numbers)

  • Train splits, every intent offered, each model with its own second temperature:
    • The v0.3 4B is worse than v0.2 on BANKING77 (0.652 against 0.690, ECE 0.044) and better on CLINC150 (0.700 against 0.666, ECE 0.056).
    • JevK5-9B: 0.734 on BANKING77 and 0.780 on CLINC150 (ECE 0.044 and 0.061).
  • Index proxy (chance-corrected skill on held-out train-split rows of 16 index benchmarks): v0.2 0.620, v0.3 4B 0.731, 9B 0.762.

Model cards: JevK5, JevK5-9B. Thanks for running the index!

Optional, lower priority: JevK5-Lite preview-1. Please keep the 4B and 9B above as the priority. If you have a spare slot, this is a third, clearly experimental row: a CPU encoder, not a JevK5 successor.

  • Weights: alibiserikbay/JevK5-Lite @ 315ee211f828a899161477c534cea23e84ba3568 (Hub tag preview-1). Apache-2.0, a 437M DeBERTa-v3-large.
  • Runtime: pip install "jevk5[lite] @ git+https://github.com/allebee/jevk5@v0.3.2", then JevK5Lite.from_pretrained("alibiserikbay/JevK5-Lite"). It runs on CPU; threads= and dtype= are optional.
  • Mapping to your rows: one head per question, all in one encoder pass.
    • The task is the question's instructions, and the labels are the option descriptions, mapped back to option ids.
    • noul becomes true/false, and score becomes its levels in order. Multi-question rows share one pass.
    • Questions with more than 16 options are answered in one pass. Long label sets extend the sequence past 512 tokens, which is how the model was trained; DeBERTa-v3 has no absolute positions.
  • Coverage: none of your request shapes that we checked are refused. States longer than the room left after the labels are truncated from the end; on JevBench's public hard tier that hit 52 of 111 items. A failed row scores 0.
  • What to expect: it is a classifier, weak on reasoning and long documents. On JevBench's 231 public items it scores easy 0.958, standard 0.750 and hard 0.405, against JevK5 v0.2's 1.000 / 0.958 / 0.739. Your GLiNER rows are the closest comparison.
  • Declared overlap: its training data includes the train splits of BANKING77 (9,171 rows), CLINC150+OOS (14,646) and SGD (3,306). They were deduplicated against your test and validation items (exact matches and shared 8-word sequences). The rest is public data outside the index (MASSIVE, HWU64, SNIPS, Bitext, DBpedia-14, Civil Comments, arXiv) and 20.8k synthetic documents that GPT-6 Luna wrote from scratch. No test or validation split of anything was trained on.

Details, the mapping snippet and the coverage list: README: JevK5-Lite on JevBench and the Decision Index.

Update for the 9B row: please run JevK5-9B v0.3.3 instead of v0.3. It uses the same training data, trained for 1.5 epochs instead of 1. The epoch count came from a sweep whose rule we fixed before the results; the card has the rule and the table. The 4B request above is unchanged.

  • Weights: alibiserikbay/JevK5-9B @ d6521a18a86999190e9d775c915af3d6d6772fc4 (Hub tag v0.3.3). v0.3 stays at the tag v0.3.
  • Runtime: unchanged. jevk5_config.json now reads temperature 1.316 and knockout_temperature 1.05. jevk5 0.3.0 or later reads both (tag v0.3.3 is the same runtime).
  • Declared overlap: identical training data to v0.3, so the statement above applies unchanged.
  • Our held-out numbers against v0.3's 9B:
    • index proxy 0.762 → 0.794, hard set 0.781 → 0.859, teacher questions 0.851 → 0.848;
    • more than 16 options: BANKING77 0.734 → 0.754, CLINC150 0.780 → 0.804 (out-of-scope recall 0.46 → 0.59).

If you have already run v0.3's 9B, replace it with v0.3.3 when convenient.

multimodalart changed discussion status to closed

Hello, can you please score it yourself (following the instructions here: https://github.com/apolinario/decision-index ) and submit as a PR to this same repo https://github.com/apolinario/decision-index ?

multimodalart changed discussion status to open

Sign up or log in to comment