knowledgator

Llama encoder 1.0B

Question answering

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
question answeringLicense: apache-2.0SHA-256 recorded for 7 of 9 filessafetensors
Quick answer: compatibility and sources

Can I run Llama-encoder-1.0B 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.

Llama-encoder-1.0B is an open-weights language model for question answering. 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: beaf3db86b8794f7c858e91b1a4ef81dd79a587a402c7ef24cde937d2c86c425. 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-knowledgator-llama-encoder-1-0b.
  • Open /artifact/hf-model-knowledgator-llama-encoder-1-0b/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-knowledgator-llama-encoder-1-0b for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-knowledgator-llama-encoder-1-0b/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
knowledgator/Llama-encoder-1.0B

Content controls: not assessed.

The catalog lists this model for answering questions. Catalog sources: license, cardMetadata.license, task, cardMetadata.pipelineTag.

Download availability is being checked.

Hashes recorded. Date not recorded.

FileTamanhoSHA-256OrigemBaixar
Weights
model.safetensors4.4 GB
beaf3db8…2c86c425beaf3db86b8794f7c858e91b1a4ef81dd79a587a402c7ef24cde937d2c86c425
Download availability is being checked.File metadata
Tokenizer & config
config.json736 bytes
29dcb35d…e8e8adfe29dcb35dab81085b39eb776117f9bf4908c8fa3a8a6ba5170b4d542de8e8adfe
Download availability is being checked.File metadata
generation_config.json111 bytes
03ad60d1…78bf6c4403ad60d1e261480774937329d6b1bcf5ea5db925360e59201f57476078bf6c44
Download availability is being checked.File metadata
special_tokens_map.json414 bytes
6fa06efa…34f5cfd06fa06efa2785e450051989a6f8fb4416b10149ded485ddd3f127a40734f5cfd0
Download availability is being checked.File metadata
tokenizer.json1.84 MB
bcd04f0e…43640f2ebcd04f0eadf90287bd26e1a183ac487d8a141b09b06aecb7725bbdd343640f2e
Download availability is being checked.File metadata
tokenizer.model499.7 KB
9e556afd…1818d3479e556afd44213b6bd1be2b850ebbbd98f5481437a8021afaf58ee7fb1818d347
Download availability is being checked.File metadata
tokenizer_config.json776 bytes
f514e7c3…8197e53af514e7c3008881b6ba7e6a0cdb44c71ce47dc335920dac143ae7bc788197e53a
Download availability is being checked.File metadata
Docs
.gitattributes1.52 KB—Download availability is being checked.File metadata
README.md5.46 KB—Download availability is being checked.File metadata

Verificar um download

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.