If my open source models have been useful to you, please consider supporting me in building small, useful AI models for everyone (and help me afford med school / help out my parents financially). Thanks! bert-large-NER is a fine-tuned BERT model that is ready to use for Named Entity Recognition and achieves state-of-the-art performance for the NER task. It has been trained to recognize four types of entities: location (LOC), organizations (ORG), person (PER) and Miscellaneous (MISC). Specifically, this model is a bert-large-cased model that was fine-tuned on the English version of the standard CoNLL-2003 Named Entity Recognition dataset. If you'd like to use a smaller BERT model fine-tuned…
Open-weight model · Token classification
bert-large-cased-finetuned-conll03-english
by Bayerische Staatsbibliothek dbmdz/bert-large-cased-finetuned-conll03-english
Runs On
What it takes to serve bert-large-cased-finetuned-conll03-english (334M parameters): the memory its weights need at each precision, and the cheapest way to rent enough data-center GPUs to hold them.
| Precision | Weights | Memory needed | Cheapest setup | Per hour | Also fits |
|---|---|---|---|---|---|
| 16-bit | 0.7 GB | 0.8 GB | 1x MI300X (192 GB) Vultr |
$1.85 | 1x H100 $1.99 · 1x MI325X $2.00 |
| 8-bit | 0.3 GB | 0.4 GB | 1x MI300X (192 GB) Vultr |
$1.85 | 1x H100 $1.99 · 1x MI325X $2.00 |
| 4-bit | 0.2 GB | 0.2 GB | 1x MI300X (192 GB) Vultr |
$1.85 | 1x H100 $1.99 · 1x MI325X $2.00 |
Memory is the weights at that precision plus 20% for the runtime and a short context; a long context needs more. Prices are the lowest on-demand hourly rates in the SAVRN Index, read Sep 18, 2026.
Model Card
The publisher has not written a card for this model.
Configuration
- Architecture
- BertForTokenClassification
- Context length (tokens)
- 512
- Layers
- 24
- Hidden size
- 1,024
- Feed-forward size
- 4,096
- Attention heads
- 16
- Vocabulary size
- 28,996
- Model type
- bert
Identity and Version
- Repository
- dbmdz/bert-large-cased-finetuned-conll03-english
- Publisher
- Bayerische Staatsbibliothek
- Task
- Token classification
- Modality
- Text
- Library
- transformers
- Parameters
- 334M parameters
- Languages
- tf, jax
- Revision
- 4c534963167c08d4b8ff1f88733cf2930f86add0
- First published
- 2022-03-02
- Last updated
- 2023-09-06
Files and Weights
9 files, 6.7 GB in total. The weights are 5 files totalling 6.7 GB in bin, h5, msgpack, ot, safetensors.
Every file
| File | Type | Size | SHA-256 |
|---|---|---|---|
| flax_model.msgpack | Weights | 1.3 GB | c475728eac2b |
| model.safetensors | Weights | 1.3 GB | 9a90b161380a |
| pytorch_model.bin | Weights | 1.3 GB | 6599da272099 |
| rust_model.ot | Weights | 1.3 GB | fa262d61c812 |
| tf_model.h5 | Weights | 1.3 GB | dfc628f7dec0 |
| config.json | Configuration | 998 B | — |
| .gitattributes | Repository | 445 B | — |
| tokenizer_config.json | Tokenizer | 60 B | — |
| vocab.txt | Tokenizer | 213.4 KB | — |
License and Download
- License
- Not stated by the source
- Access
- Open weights, no gate
- Download size
- 6.7 GB
Released by Bayerische Staatsbibliothek through its official repository on Hugging Face.
Memory Requirements
| Precision | Weights in memory |
|---|---|
| As published | 6.7 GB |
| 16-bit | 0.7 GB |
| 8-bit | 0.3 GB |
| 4-bit | 0.2 GB |
Weights only, from the published parameter count; the key-value cache and runtime add to this.
Questions About bert-large-cased-finetuned-conll03-english
How much GPU memory does bert-large-cased-finetuned-conll03-english need?
About 0.8 GB at 16-bit and 0.2 GB at 4-bit: the weights (334M parameters) plus a working margin. A long context needs more.
What is the cheapest GPU to run bert-large-cased-finetuned-conll03-english on?
At 16-bit, 1x MI300X from $1.85 an hour; at 4-bit, 1x MI300X from $1.85 an hour, at the lowest on-demand prices the SAVRN Index lists.
What is bert-large-cased-finetuned-conll03-english's context length?
512 tokens, from the maximum position embeddings in its published configuration.
Similar Models
Specialized model for Disease Entity Recognition - Disease entities from the BC5CDR dataset This model is a state-of-the-art fine-tuned transformer engineered to deliver enterprise-grade accuracy for disease entity recognition - disease entities from the bc5cdr dataset. This specialized model excels at identifying and extracting biomedical entities from clinical texts, research papers, and healthcare documents, enabling applications such as drug interaction detection, medication extraction from patient records, adverse event monitoring, literature mining for drug discovery, and biomedical knowledge graph construction with production-ready reliability for clinical and research applications.…
Specialized model for Gene Entity Recognition - Gene-related entities This model is a state-of-the-art fine-tuned transformer engineered to deliver enterprise-grade accuracy for gene entity recognition - gene-related entities. This specialized model excels at identifying and extracting biomedical entities from clinical texts, research papers, and healthcare documents, enabling applications such as drug interaction detection, medication extraction from patient records, adverse event monitoring, literature mining for drug discovery, and biomedical knowledge graph construction with production-ready reliability for clinical and research applications. This model can identify and classify the…
A RoBERTa [[Liu et al., 2019]](https://arxiv.org/pdf/1907.11692.pdf) model fine-tuned for de-identification of medical notes. A token can either be classified as non-PHI or as one of the 11 PHI types. Token predictions are aggregated to spans by making use of BILOU tagging. The PHI labels that were used for training and other details can be found here: Annotation Guidelines More details on how to use this model, the format of data and other useful information is present in the GitHub repo: Robust DeID. A demo on how the model works (using model predictions to de-identify a medical note) is on this space: Medical-Note-Deidentification. Steps on how this model can be used to run a forward…
GLiNER2.5 Multi is the multilingual boundary checkpoint. It is built on mDeBERTa-v3-base and is the default choice when you need entities, classification, records, and relations in one model across languages. Load it with AutoExtractor: the checkpoint's architecture field selects BoundaryExtractor automatically. Fine-tune via Fastino. Join discussions on Reddit. This card is for fastino/gliner2.5-multi-v1. All three checkpoints share the same public API. Python 3.10 or newer is required. The [local] extra pulls in PyTorch so you can load Hub checkpoints. Always use AutoExtractor for GLiNER2.5. GLiNER2.frompretrained(...) is the legacy span loader and will not dispatch this checkpoint.…
Model · Token classification
piiranha-v1-detect-personal-information
william (at) integrinet [dot] org Piiranha (cc-by-nc-nd-4.0 license) is trained to detect 17 types of Personally Identifiable Information (PII) across six languages. It successfully catches 98.27% of PII tokens, with an overall classification accuracy of 99.44%. Piiranha is especially accurate at detecting passwords, emails (100%), phone numbers, and usernames. Performance on PII vs. Non PII classification task: Piiranha was trained on H100 GPUs generously sponsored by the Akash Network Piiranha is a fine-tuned version of microsoft/mdeberta-v3-base. The context length is 256 Deberta tokens. If your text is longer than that, just split it up. Supported PII types: Account Number, Building…