llm-jp

llm jp 3 1.8B

Chat

This receipt records checks for this exact file; it does not prove safety or that it will run on your device. Read the receipt

Model details
text generationLicense: apache-2.0SHA-256 recorded for 6 of 8 filessafetensors
Quick answer: compatibility and sources

Can I run llm-jp-3-1.8b-instruct on my computer?

It depends on your memory, processor, file format and runtime. A download is not confirmed by the current file evidence; inspect the file record before trying it. A file-size fit is an estimate, not a successful run or speed promise. Read the license before use.

llm-jp-3-1.8b-instruct is an open-weights language model for text generation. Model weights are learned parameters; a runtime loads them. A hosted file is an individual file Hugging Bay can serve. SHA-256 identifies exact file bytes. The availability date above applies to this file record, not the upstream metadata update date.

As of the recorded file availability check on .

Recorded SHA-256 for model.safetensors: 300cfd5b4aa095c6e280778e815f049f9a5ebfcae584cc2d9fd6b629dbbd80b7. Exact file evidence · Machine-readable source facts · Run evidence and any recorded receipts. A checksum fingerprints only the named file bytes; it does not prove safety, quality, a complete multi-file selection or a successful run.

Updated · Page-copy source revision 8871bab84e1cf80aea1686a944ec335078a6c036 · Source files: apps/web/lib/model-page-template.mjs, apps/web/lib/model-page-v3.mjs, apps/web/lib/aeo-page.mjs · Full revision record

Model metadata: As of at the model source. Popularity counters are source-reported, not measured by Hugging Bay. Availability checked .

Key facts

Catalog record
Summarizes upstream metadata; it is not itself a download or run receipt.
File evidence
Lists exact filenames, availability and any recorded SHA-256 for individual files.
Run evidence
Reports measured results only when a receipt exists for named file bytes and a setup; otherwise unmeasured.
Checksum scope
SHA-256 fingerprints one file’s bytes; it does not prove safety, quality or a multi-file bundle.

Evidence you can inspect (plain text)

  • This page’s quick answer names the file record for hf-model-llm-jp-llm-jp-3-1-8b-instruct.
  • Open /artifact/hf-model-llm-jp-llm-jp-3-1-8b-instruct/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-llm-jp-llm-jp-3-1-8b-instruct for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-llm-jp-llm-jp-3-1-8b-instruct/card.md for machine-readable source facts (not a runtime test).
  • A matching checksum on this page fingerprints only the named bytes shown in file evidence.

Unmeasured states are stated explicitly; this page does not invent run scores or compatibility guarantees.

Which date applies to which fact

  • File availability check:
  • Committed page-copy sources:
  • Upstream model metadata: Dates on artifact records when shown; not implied by page-copy revision
  • Run receipts: Only on /evidence pages when recorded; otherwise unmeasured

Page-copy revision (Updated line above) identifies committed text sources, not upstream model edits or test outcomes.

Requirements and source record

Try browser chat with a small demo model (a separate model; device support is checked before loading).

llm-jp/llm-jp-3-1.8b-instruct

Content controls: not assessed.

The catalog lists this model for having conversations. Catalog sources: license, cardMetadata.license, tags, task, cardMetadata.pipelineTag.

Download availability is being checked.

Hashes recorded. Date not recorded.

FileTamañoSHA-256OrigenDescargar
Weights
model.safetensors3.74 GB
300cfd5b…dbbd80b7300cfd5b4aa095c6e280778e815f049f9a5ebfcae584cc2d9fd6b629dbbd80b7
Download availability is being checked.File metadata
Tokenizer & config
config.json678 bytes
ee05f7d2…f1513a54ee05f7d22edd452390a31716765c5052bd142866c3cd1a42c2a8464ff1513a54
Download availability is being checked.File metadata
generation_config.json111 bytes
03ad60d1…78bf6c4403ad60d1e261480774937329d6b1bcf5ea5db925360e59201f57476078bf6c44
Download availability is being checked.File metadata
special_tokens_map.json996 bytes
26a31457…259ec5ab26a314575f93e92920df4aacab5af1d6fe5f7f5bb5fc9c8cef2fd738259ec5ab
Download availability is being checked.File metadata
tokenizer.json6.41 MB
d0fcf4e1…59065219d0fcf4e1e7a08e855273824678363335b0cd707937332ec1cc48eee259065219
Download availability is being checked.File metadata
tokenizer_config.json2.37 KB
4445f8a2…e48203104445f8a23d0cd9eccf3dcf4ec818ea0dc3c8b3b8f438ab91df979b1be4820310
Download availability is being checked.File metadata
Docs
.gitattributes1.52 KB—Download availability is being checked.File metadata
README.md8.7 KB—Download availability is being checked.File metadata

Comprobar una descarga

In the folder where you saved config.json, run:

macOS
shasum -a 256 -- 'config.json'
Linux
sha256sum -- 'config.json'
Windows
Get-FileHash -LiteralPath 'config.json' -Algorithm SHA256

Compare the result with the recorded SHA-256.