Evidence review · 11 minute read

Benchmarks, with the caveats attached.

The useful question is not whether one model “wins.” It is which checkpoint was tested, on what distribution, with what calibration and whether the comparison was actually run side by side.

Source policy. “Project-reported” means the number comes from Laya’s own reproducible result files. “Published Jev” means imported from an external Jev result, not re-run by Laya. “Independent” means a separate repository, with its sample-size limits shown.

Project-reported headline results

DatasetLaya resultJev published resultImportant context
typed-decisions0.7660.727Laya’s workflow-specific fine-tuned checkpoint
AG News0.9500.910AG News was in Laya’s training mix
DAIR Emotion0.5950.480Held out for Laya
Banking770.425 on 77 labels0.870 on 72 labelsClear high-cardinality weakness at default budget

These numbers are not one controlled head-to-head run. The Laya project explicitly says it had no TypeSafe API access and that prompts and sample sizes may differ. Treat the comparison as directional.

The checkpoint matters more than the brand name

Model on typed-decisionsAccuracySoft accuracyBrier ↓ECE ↓
laya-typed-decisions0.7660.4710.0620.213
laya0.3620.3320.3160.175
laya-multilingual0.3420.3260.4390.285
Jev 1.13.0, published0.7270.5800.1480.144
Majority-class baseline0.461

The base Laya checkpoints are below the majority-class baseline here. The impressive result belongs to specialization. Jev better matches the teacher’s full probability distribution and has better unadjusted ECE in this table.

Latency on a Tesla T4

Questions in one callEnglish LayaLaya multilingual
139.5ms32.8ms
584.5ms40.1ms
10158.6ms72.3ms
50771.3ms337.4ms

These are warm local GPU timings. A production router can take roughly 7–10 seconds when it must swap checkpoints, according to the repository, so servers handling multiple languages should preload the models they serve.

Multilingual evidence

On MASSIVE intent classification with 20 options, the multilingual checkpoint reaches 0.366 macro accuracy across 51 languages and clears the project’s “three times random” usability bar in 45 of them. The English model reaches 0.227 macro accuracy and clears that bar in 23.

“Supports 100+ languages” describes the encoder’s intended coverage, not verified performance in 100 production settings. Public evaluation covers 51 languages, and results vary widely. Routing is part of the product, not an optional optimization.

Application themes

ThemeBest reported checkpoint resultTraining status / caution
Email spam0.993In training mix
Phishing0.993In training mix
LLM guardrails0.762Held out
Moderation0.530Held out; weak macro-F1
RAG relevance0.657In training mix
Support triage, 10-way0.522In training mix
Model routing0.659Held out; English checkpoint

A polished demo can make moderation look solved, while the held-out result says otherwise. Production evaluation should include natural class imbalance, ambiguous cases and adversarial inputs—not only clear examples.

Calibration repair

The repository reports mean ECE changing from 0.466 to 0.081 for the English checkpoint and from 0.314 to 0.106 for multilingual after fitting temperatures by question type and option count. Those post-fit values are encouraging, but calibration fitted on one distribution can drift on another.

Independent evidence: useful, but small

A separate M4 Max test compared multilingual Laya-MLX with Jev 1.13 on 40 Chinese support-ticket cases. Jev scored 31/40; Laya scored 23/40. Laya’s warm local latency was 7.6ms versus a 588ms Jev API call. At a selected cascade threshold, the test matched Jev accuracy while sending 55% of cases to Jev.

The author clearly notes the limits: one task, one machine, one small test set and arguable labels. It should generate hypotheses, not headline claims.

A responsible evaluation checklist

  1. Freeze a labelled set before tuning prompts, criteria or thresholds.
  2. Report the exact checkpoint, package version, hardware and context limits.
  3. Measure macro-F1 and per-class recall alongside aggregate accuracy.
  4. Plot reliability by confidence bucket and inspect confident errors.
  5. Shuffle option order and test paraphrases.
  6. Include ambiguous, empty and out-of-scope inputs.
  7. Separate warm inference from model loading and end-to-end service latency.

Main data source: Laya BENCHMARKS.md and linked raw result files. Independent sample: laya-jev-lab. Values were transcribed on 22 September 2026 and may change.