AIToday
Large Language ModelsQiita 機械学習Published: Nov 1, 2026, 19:01 JST

Liquid AI's d1-2B trails d1-3B on 3 Japanese benchmarks

Send on LINE
Liquid AI's d1-2B trails d1-3B on 3 Japanese benchmarks

3 Key Points

  1. What happened

    Liquid AI's d1-2B scored 75.4 on JNLI, 86.6 on JCommonsenseQA and 64.2 on Livedoor news classification, below d1-3B's 81.2, 90.2 and 68.1.

  2. Why it matters

    The model card's claim that the smaller d1-2B beats d1-3B on most decision benchmarks does not carry over to these Japanese-language tasks, so teams picking a model by card figures may see different results.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

Liquid AI added d1-2B to its open-weight d1 family, with the Hugging Face repository created on October 24 and the first commit on October 27 — roughly three weeks after d1-3B and d1-omni-600M appeared on October 5. d1-2B is a decision model rather than a text generator: it returns a probability-scored answer in one pass, taking state (text or JSON), images and video, and questions such as yes/no, multiple choice, graded rating, value extraction and object location. It has 1.92B parameters, was post-trained from Liquid AI's LFM3-VL-2B vision-language model, supports 16 languages including Japanese, and is under the LFM Open License v1.0; the model card does not state a release date.

The comparison is not a like-for-like new measurement of every model. Only d1-2B was measured for this article, while d1-3B and d1 API figures come from earlier runs, and the author notes the possibility that the API or weights changed in between. The model card's table and this article's results can appear to conflict, but the benchmarks differ in content, so the author does not treat that as a contradiction — limited to Japanese sentence relations, commonsense and article classification, d1-3B was more accurate. Against other models, d1-2B sits close to Jeff Gemma4-E2B among locally run weights; the author did not run significance tests on those three differences. ModernBERT-Ja-310M was fine-tuned on each benchmark's training data, making its conditions different from the others.

FAQ
How was d1-2B tested?
On 2026-11-01, using a single RTX 4080 at bfloat16 without compile, one request at a time with parallelism 2, via model.system_one(state, questions), at repository commit 10e7671.
Did the author re-measure d1-3B and d1 API?
No. d1 API was measured on October 1 and d1-3B on October 8; the same items, order and request shape were used.
How did d1-2B respond speed-wise?
Median latency was 12 ms on JNLI and 42 ms on Livedoor, about 25% shorter than d1-3B in both benchmarks.
Qiita 機械学習Read Original Article
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleAI skips ./bin/scan unless told; 1 line fixes it