Will it last?
This page is a projection of the one entry record, the Transparency factor that Support covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.
- AssessUse & modify + Transparency
- ImplementData control + Reliability
- UseReliability
- SupportTransparency
Common problems & fixes
From the cookbook and cards (ev-cookbook, ev-gguf); not an exhaustive catalogue:
- Garbled or unparsed output, broken tool calls: You are using the wrong tokenizer or
skipping the template. Load the bundled tokenizer, call
apply_chat_template, and do not use theopenai-harmonytokenizer. - Reasoning text mixed into the answer on vLLM: Start the server with the
llmjp4reasoning parser fromllm-jp-vllm0.1.1 or later and vLLM 0.30.0 or later. - llama.cpp chat parsing fails: Use upstream v0.6.0 or later and a 4.1 GGUF; the GGUF card still says a fork is needed, so if upstream fails, try the publisher fork named on the card.
- Special-token text in user input: Input that resembles
<|...|>may need custom encoding; parse token IDs instead of decoded text. - Wrong whitespace in decoded text: The vLLM example documents that
output.textloses whitespace; decodeoutput.token_idswith the model tokenizer.
Versions, changelog & cadence
Hugging Face creation dates (ev-hub-api), the corpus pages (ev-corpus-v41) and the announcement
(ev-blog, ev-pcwatch):
| Date | Release |
|---|---|
| 2026-03-15 and 16 | LLM-jp-4 8B base, 8B thinking, 32B-A3B base and thinking |
| 2026-03-30 | llm-jp-4-8b-instruct |
| 2026-08-14 | LLM-jp-4 33B base and thinking |
| 2026-09-15 and 16 | LLM-jp-4.1 8B, 32B-A3B and 33B thinking |
| 2026-09-24 | official 4.1 GGUF builds |
| 2026-09-28 | 4.1 announcement on the NII blog; the repositories were last modified the same day |
| 2026-10-14 | LLM-jp-4 technical report on arXiv (v1; 33B results to follow) |
Revisions are Hugging Face commits; there is no tagged changelog for the weights. The cards link corpus changelogs (for example corpus v4.1 on 2026-03-31 and 2026-04-14). Pin the commit hash.
Community & support channels
The cards give llm-jp(at)nii.ac.jp for questions and a survey form for reporting how the
models are used (ev-card-41). Hugging Face discussion tabs exist on the model repositories (none
had been opened on the 33B repository on 2026-11-19). The release page lists tools and corpora on
GitHub and GitLab (ev-release-page). NII announced a trial API and chat service through the
University of Tokyo mdx-MaaS, mainly for researchers (ev-pcwatch). No community forum or
commercial support is listed.
Tracked known issues
No public issue tracker exists for the models; these are issues stated in publisher documents:
- the GGUF card and the cookbook disagree on whether llama.cpp needs a fork (
ev-gguf); - LLM-jp-4.1 uses a modified Harmony template and is not compatible with the
openai-harmonylibrary tokenizer (ev-card-41); - original 4.0 GGUF chat templates lack the declaration needed to select the 4.1 parser
(
ev-cookbook); - AIME, GPQA Diamond and long-context tool use remain well behind Qwen3.5 (
ev-blog); - the models "may still generate inaccurate, inappropriate, or otherwise undesirable outputs"
(
ev-card-41).
How this scores
The ownership factor this domain covers, drawn from the one entry record.
TransparencyDo you know what it is: weights, training, behaviour, and legible terms?
StrongCorpora, SFT and DPO data and pre-training scripts are public with per-source licences and a technical report, with named exclusions (NWJC, Ceek.jp News, ichikara, AnswerCarefully) and no confirmed 4.1 post-training code (ev-techreport, ev-corpus-v4, ev-sft-dpo, ev-code).
Sources
The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.