Model page

tartuNLP/Llama-3.1-EstLLM-8B-Instruct-1125 warn

downloads 628likes 6license llama3.1arch llamaparams 8030.3Mupdated 2026-08-13

claims base: tartuNLP/Llama-3.1-EstLLM-8B-Instruct-0825, meta-llama/Llama-3.1-8B-Instruct · chat template: present · view on Hugging Face ↗

Scan coverage

Ingot runs three batteries against a model. What each one checks →

BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-21
Weights batteryWeights forensics — no GPU, no downloadcomplete 2026-08-21128,256-token embedding scanned · 499 undertrained · lineage consistent
Behavioral batteryLive-inference differentialsnot run

Findings

Scanned 2026-08-21 · published from a community scan.

medium Undertrained (glitch) token surface in vocabulary

Embedding-norm scan flagged 499 undertrained tokens (norm < 0.3× the vocabulary median of 0.694), including 148 plain-ASCII strings that can appear in ordinary input as identifiers — e.g. "$PostalCodesNL", "ForCanBeConverted", "TokenNameIdentifier", "useRalative", "ForCanBeConvertedToF", "PostalCodesNL", "ilmektedir", "CLIIIK". In models where this class was tested behaviorally, such tokens silently rewrote user input into confident, schema-valid, wrong output. These are candidates from the weights alone; behavioral confirmation requires the behavioral battery.

How to fixruntime guardweight-level

Keep the affected token strings out of the model's input — the scan-derived runtime guard carries this model's exact blocklist.

  1. Fetch this model's guard artifact (`/api/v1/guard/<owner>/<model>`): the confirmed corrupting tokens and the low-norm candidate list, derived from the published scan.
  2. Screen inbound text with it (the `@ingotai/guard` package is a reference implementation) and route flagged records to a different model or human review — verbatim-copy tasks on flagged strings are the failure mode.
  3. The underlying cause is undertrained embeddings in the weights; a true fix is weight-level (continued pretraining on the affected tokens) — that is not a patch, it's a training job.

info Weights consistent with claimed parent tartuNLP/Llama-3.1-EstLLM-8B-Instruct-0825

Mean cosine similarity of 64 sampled token-embedding rows against tartuNLP/Llama-3.1-EstLLM-8B-Instruct-0825 is 1.000 — the weights plausibly descend from the declared base (relation: unspecified).

How to fix

Fix or verify the `base_model` declaration so lineage checks can run.

  1. If you own the repo: correct the `base_model` field in the model card metadata to the real, public parent.
  2. If you don't: identify the true parent (config architecture + weight shapes narrow it fast) and re-scan with that lineage in mind.

Remediation guidance addresses the documented findings only. It is evidence-driven repair, not a safety certification of the model.

Fingerprint

The durable profile of this model: measured weights-and-metadata facts, rebuilt on every scan and battery run. Updated 2026-08-21.

architecturellama · 32 layers · 4096-dim
parameters8030.3M
vocabulary128,256 tokens
licensellama3.1
serializationsafetensors
chat templatenone
claimed lineagetartuNLP/Llama-3.1-EstLLM-8B-Instruct-0825, meta-llama/Llama-3.1-8B-Instruct
lineage verifiedconsistent vs tartuNLP/Llama-3.1-EstLLM-8B-Instruct-0825 — embedding-row cosine 1.000
glitch-token surface499 undertrained candidates, 148 plain-ASCII
Full measured fingerprint
architecturesLlamaForCausalLM
librarytransformers
pipelinetext-generation
repo files17
revision9e400db48fbb
HF snapshot638 downloads · 6 likes · updated 2026-08-13 · captured 2026-08-21
embedding tensormodel.embed_tokens.weight · BF16 · 128,256×4096
embedding normsmedian 0.6944 · mean 0.6797
lineage checkconsistent — cosine 1 over 64 sampled rows vs tartuNLP/Llama-3.1-EstLLM-8B-Instruct-0825
glitch-token samples"$PostalCodesNL", "ForCanBeConverted", "TokenNameIdentifier", "useRalative", "ForCanBeConvertedToF", "PostalCodesNL", "ilmektedir", "CLIIIK", "_ComCallableWrapper", "krvldkf", "webElementXpaths", "sahuje"

Battery runs

The run trace behind the findings above: every deep-battery job for this model, with what each run measured or why it failed. Findings are only as good as the runs that produced them.

batterystatusqueueddurationattempts
weightscomplete2026-08-21 05:144m1
weights run 2026-08-21 measurements
probes runglitch-norm-scan, lineage-norm-correlation
embedding tensormodel.embed_tokens.weight · BF16 · 128,256×4096
glitch surface499 undertrained, 148 plain-ASCII
lineage checkconsistent — cosine 1 over 64 rows vs tartuNLP/Llama-3.1-EstLLM-8B-Instruct-0825

Verdict badge

Ship the verdict in your README — it always shows the latest published analysis:

Ingot verdict: warn

[![Ingot scan](https://ingot.tools/api/v1/models/tartuNLP/Llama-3.1-EstLLM-8B-Instruct-1125/badge.svg)](https://ingot.tools/models/tartuNLP/Llama-3.1-EstLLM-8B-Instruct-1125)
Gate it in CI