Dizex

FoodBaseBERT NER

Classify & tag

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
token classificationLicense: mitSHA-256 recorded for 7 of 10 filessafetensors · BIN
Quick answer: compatibility and sources

Can I run FoodBaseBERT-NER 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.

FoodBaseBERT-NER is an open-weights language model for token classification. 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: a4dbf739caf6fe66972e3a7db21583fdf2f90cdf6854d65e295a0417772be3cd. 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-dizex-foodbasebert-ner.
  • Open /artifact/hf-model-dizex-foodbasebert-ner/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-dizex-foodbasebert-ner for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-dizex-foodbasebert-ner/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
Dizex/FoodBaseBERT-NER

Content controls: not assessed.

The catalog lists this model for labeling parts of text. Catalog sources: license, cardMetadata.license, task, cardMetadata.pipelineTag.

Download availability is being checked.

Hashes recorded. Date not recorded.

FileTamañoSHA-256OrigenDescargar
Weights
model.safetensors430.9 MB
a4dbf739…772be3cda4dbf739caf6fe66972e3a7db21583fdf2f90cdf6854d65e295a0417772be3cd
Download availability is being checked.File metadata
pytorch_model.bin431 MB
52ad3e81…e757194452ad3e81e6758cf978463dae68f58981e534220df3d0ec0bfddfde50e7571944
Download availability is being checked.File metadata
Tokenizer & config
added_tokens.json20 bytes
cca384ab…ceaafac8cca384abe5a2456c20262edfae2e263d744c33441a4ccd54d3034218ceaafac8
Download availability is being checked.File metadata
config.json814 bytes
2c9b88c7…e1d6facf2c9b88c7fb8fd7186a24407e7b1e6fbc6a3370a02e078da2b06dfd93e1d6facf
Download availability is being checked.File metadata
special_tokens_map.json125 bytes
b6d346be…76237ee3b6d346be366a7d1d48332dbc9fdf3bf8960b5d879522b7799ddba59e76237ee3
Download availability is being checked.File metadata
tokenizer.json669.1 KB
74c7a295…9034aec274c7a29545cfa276982055bb8d5f7a2ee033c7b85cd50770454fc98f9034aec2
Download availability is being checked.File metadata
tokenizer_config.json350 bytes
c0715051…636d2e72c07150517c9b409def9f262623a197bfcb7576717dd7cedd6602e67c636d2e72
Download availability is being checked.File metadata
vocab.txt213.4 KB—Download availability is being checked.File metadata
Docs
.gitattributes1.43 KB—Download availability is being checked.File metadata
README.md1.32 KB—Download availability is being checked.File metadata

Comprobar una descarga

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

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

Compare the result with the recorded SHA-256.