Model
LLM-jp-4.1 thinking
Publisher
Research and Development Center for Large Language Models (LLMC), National Institute of Informatics (NII), Japan - LLM-jp consortium (JP)
Openness
open_weights_recipe
Licence
Apache License 2.0
You own the weights, the data lineage and the right to run and change them: Apache-2.0, ungated, with public corpora, SFT and DPO sets and pre-training scripts, so this is one of the most transparent models reviewed. You do not own a deployable safety case: the publisher says the models are for research and development and not for direct production use, offers one self-run Japanese safety benchmark, no guard model and no independent test. Ownership moves to substantial if an independent evaluation lifts safety to 3 or more, and you can reach that yourself by running your own safety and jailbreak tests behind your own guard.
Do you really own it?
Partial
none·limited·partial·substantial·full
Analytical input: AOI D · 54.4/100
The four ownership factors
Floor-weighted, not averaged. Reliability is weak, and the weakest factor sets the ceiling, so the verdict stays partial however strong the rest.
1
Use and modify freelyCan you run, modify and adapt it with no gate and no field-of-use trap?
StrongApache-2.0, ungated, safetensors and GGUF, with public base models and SFT and DPO data, so you can run, fine-tune and commercialise it; the production disclaimer is card text, not a licence restriction (ev-license, ev-card-41).
How this scores (AOI sub-dimensions)
Openness4/5how much is released - weights, data, code, licence - and how freelyOpen weights under Apache-2.0 plus a published recipe: pre-training and mid-training corpora on public GitLab with per-subcorpus licences, SFT and DPO datasets on Hugging Face, pre-training and mid-training scripts and installers on GitHub (Apache-2.0), and a technical report that states data-selection criteria.
Legal3/5how permissive and clean the licence is for real commercial useApache-2.0 grants copyright and patent rights with no field-of-use clause, so commercial and production use is licensed.
2
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).
How this scores (AOI sub-dimensions)
Provenance2/5how well we can trace and verify what went into the modelThe canonical source is identifiable (the NII release page links to huggingface.co/llm-jp), weights are safetensors with per-file sha256, the hub scan reports no flagged files and the org publishes official GGUF builds.
Governance3/5how accountable and well-documented the publisher isA national research institute with named authors and a public release record: 4.0 in March 2026, 33B in August, 4.1 in September, technical report in October.
3
ReliabilityIs it reliable and good enough for the job?
WeakSafety scores 2: one publisher-run Japanese benchmark, no independent evaluation or guard model, and the publisher says the models are not for direct production use; operational is 3 (ev-card-41, ev-blog, ev-cookbook).
How this scores (AOI sub-dimensions)
Operational3/5how practical it is to run, serve and maintain in productionRuns on Hugging Face Transformers, vLLM and llama.cpp with a maintained Apache-2.0 cookbook, official GGUF builds in BF16 and Q4_K_M, a 64K context and a Q4_K_M 33B validated on a local GPU.
Safety2/5whether misuse risks are evaluated and guardrails are providedThe 4.1 models are safety post-trained (the card says SFT and DPO "for instruction following and safety", and the report describes an upsampled Japanese safety set and safety-judged preference pairs), and the residual risk is disclosed.
4
Doesn't extract your dataDoes running it keep your knowledge and data yours?
StrongSelf-hosted weights under Apache-2.0 with no telemetry or claw-back; review the two repository Python files that run under trust_remote_code (ev-license, ev-hub-api).
How this scores
Not a scored AOI dimension. For a self-hosted model, data-control is a structural property of running the weights yourself, strong by default unless the model phones home or the licence claws back rights. For a hosted API this factor is the retention + train-on-inputs + residency read, scored from the binding terms.
How the AOI score is computed
The seven dimensions above, each scored 0 to 5, weighted and summed to the 0 to 100 headline. The score is the analytical input behind the ownership verdict, not the verdict itself.
DimensionScoreWeightPoints
Openness4/50.1814.4
Provenance2/50.166.4
Legal3/50.169.6
Safety2/50.166.4
Performance2/50.145.6
Operational3/50.127.2
Governance3/50.084.8
HeadlineD · 54.4/100
Sources
Every rating traces to a primary document. Read means the text was verified; unverified means it is known to exist but has not yet been read.
DocumentWhat it grounds
Model cardread2026-11-19
The llm-jp-4.1-33b-thinking model card declares Apache-2.0 in the front matter and 11.7T tokens; the 8B and 32B-A3B cards are identical on the points used.
Model cardread2026-11-19
The LLM-jp-4 (4.0) base, 33b-thinking and 8b-instruct cards say "The models released here are in the early stages of our research and development and have not been tuned to ensure outputs align with human intent and safety considerations".
Licenceread2026-11-19
Apache-2.0 is declared in the card front matter and License section of all three 4.1 cards and in section 2.4 of the technical report.
Technical_reportread2026-11-19
The LLM-jp-4 Technical Report (arXiv 2610.19331 v1, 2026-10-14) covers 8B dense and 32B-A3B MoE models trained from scratch on about 12T tokens.
Documentationread2026-11-19
LLM-jp Corpus v4.1 README: English FineWeb-Rescored and MegaMath-Web-Pro-Max-OSS (ODC-BY plus Common Crawl terms) and The Stack v2 code (per-repository licences), hosted on a public GitLab project; copyright stays with original authors; document-removal contact given.
Documentationread2026-11-19
LLM-jp Corpus v4 README lists Japanese, English, Korean, Chinese and code subcorpora with licences (mostly CC BY, ODC-BY, CC BY-SA).
Documentationread2026-11-19
LLM-jp Corpus Midtraining v2 README: 13 English and 2 Japanese sources with licences, including the nemotron_pretraining_code_v2 corpus (491B tokens) under the NVIDIA Data Access Agreement for Model Training and llm-jp-IPT_v0.3.2 under "Various licenses".
Documentationread2026-11-19
The llm-jp-4.1 SFT and DPO dataset cards (ungated) list per-subset licences, and responses were generated with gpt-oss-120b.
Documentationread2026-11-19
github.com/llm-jp/scripts (Apache-2.0) holds LLM-jp-4 pre-training and mid-training configurations (v4-8b, v4-32b which matches the 33B dimensions, v4-32b-a3.8b), installers, corpus-building and checkpoint-conversion scripts.
Documentationread2026-11-19
The Apache-2.0 llm-jp-4-cookbook documents Transformers 5.0.0 or later, vLLM 0.30.0 or later with llm-jp-vllm 0.1.1 or later, and llama.cpp v0.6.0 or later.
Model cardread2026-11-19
The official llm-jp-4.1-33b-thinking-gguf card (modified 2026-10-20) says running with llama.cpp "currently requires a fork of llama.cpp", which contradicts the cookbook; the repositories hold BF16 (66.4 GB) and Q4_K_M (20.4 GB) GGUF files and an imatrix.
Documentationread2026-11-19
The Hugging Face API lists the three 4.1 repositories as ungated, with safetensors BF16 shards carrying LFS sha256, no pickle files, no LICENSE file and a completed hub scan with no flagged files.
Documentationread2026-11-19
The NII release page lists the 4.1 models, corpora and fine-tuning scripts and says "Users of this model are requested to use it appropriately and at their own responsibility, in accordance with" Japan's December 2025 AI R&D and utilisation guideline.
Vendor announcementread2026-11-19
Publisher blog (2026-09-28, Japanese): 4.1 improves post-training for STEM and adds tool calling, the first LLM-jp series with it.
Third-party analysisread2026-11-19
PC Watch (Impress, 2026-09-29) reports that NII released the three LLM-jp-4.1 models on 2026-09-28 and that Apache License 2.0 applies to all.
Documentationunverified2026-11-19
The AnswerCarefully dataset (safety training data and benchmark) is gated (manual approval, licence:other); its LICENSE and README returned HTTP 401, so its terms are documented but unverified.