/ Модель

Характеристики

Контекст
512 токенов
Параметры
306 млн
Лицензия
Apache 2.0
Архитектура
deberta-v2 · dense
Базовая модель
mdeberta-v3-base
Библиотека
transformers
Опубликована
7 авг 2026

snerta-8l-base

Разметка токеновТекст → label

Многоязычная модель на базе mDeBERTa V3 для извлечения именованных сущностей из текстов на восьми славянских языках.

9скачиваний за 30 дней0лайковвеса обновлены7 авг 2026

Бенчмарки

Как модель справилась с задачами пользователей ailist и что о ней публикуют открытые лидерборды

Публичные оценки

Из открытых лидербордов. Сравнивайте результаты одного теста при одинаковых условиях — отсутствие оценки не значит, что модель хуже.

В подключённых источниках результатов для этой модели пока нет.

Что умеет модель

Описание составлено по карточке модели и метаданным Hugging Face

Snerta-8l Base — многоязычная модель распознавания именованных сущностей, разработанная авторами исследования о переносе между славянскими языками. Это дообученная версия microsoft/mdeberta-v3-base с архитектурой DeBERTa V2, примерно 306 млн параметров по метаданным и контекстом 512 токенов. Модель размечает текст в формате IOB2, выделяя людей, места, организации и сущности категории MISC.

Модель предназначена для извлечения именованных сущностей из текстов на болгарском, чешском, хорватском, польском, русском, словенском, сербском и украинском языках. Её можно использовать для обогащения документов, поиска, мониторинга СМИ, анализа корпусов и аналитики по сущностям. Обучение проведено на объединённых вручную размеченных наборах для восьми языков; для последовательностей длиннее 256 токенов README указывает усечение, если приложение не реализует разбиение на окна.

Качество может различаться между языками и предметными областями: тестирование основано на случайном разбиении предложений и не измеряет обобщение на новые документы, периоды или домены. Возможны ложные срабатывания и пропуски, особенно для редких сущностей; модель не следует применять как единственное средство анонимизации, контроля доступа или принятия юридически значимых решений. Лицензия модели — Apache-2.0, при этом обучающие корпуса сохраняют собственные лицензии и условия доступа, которые неоднородны.

Сценарии применения

  • извлечение имён людей из русскоязычных текстов
  • поиск организаций и мест в документах на славянских языках
  • обогащение документов сущностями для поиска
  • мониторинг упоминаний в СМИ
  • анализ и разметка текстовых корпусов

Ограничения

Качество различается по языкам и доменам; случайное разбиение предложений не подтверждает обобщение на новые документы или области, а редкие сущности могут распознаваться хуже. Последовательности усекаются на 256 токенах без оконной обработки; не следует полагаться на модель как на единственное средство для анонимизации или решений с высокими ставками.

Карточка модели

README от автора на Hugging Face, как он его опубликовал

Открыть на Hugging Face

Snerta-8l Base

Snerta-8l Base is a multilingual named entity recognition model for eight Slavic languages. It is a 278M-parameter microsoft/mdeberta-v3-base model fine-tuned on the complete, deduplicated training pool of the eight manually annotated language datasets prepared for the paper When Is Multilingual Transfer Beneficial for Slavic Named Entity Recognition?

Unlike Snerta-12l Base, this checkpoint does not use the lower-confidence WikiANN / PAN-X auxiliary datasets for Bosnian, Macedonian, Slovak, or Albanian.

The model recognises four coarse entity types in IOB2 format:

TypeMeaning
PERPerson
LOCLocation
ORGOrganization
MISCMiscellaneous entity, including source-specific labels mapped into the shared category

The underlying nine labels are O, B-LOC, I-LOC, B-MISC, I-MISC, B-ORG, I-ORG, B-PER, and I-PER.

Intended use

The model is intended for general-purpose named entity extraction from Bulgarian, Czech, Croatian, Polish, Russian, Slovene, Serbian, and Ukrainian text. It is particularly useful when one shared model is preferable to maintaining a separate model for every language and training exclusively on the eight manually annotated language pools.

It is suitable as a component in search, document enrichment, media monitoring, corpus analysis, and entity-centric analytics. It should not be used as the sole mechanism for anonymisation, access control, legal decisions, or other high-stakes applications. Validate it on the target domain and language before deployment.

Usage

Install Transformers and create a token-classification pipeline with simple entity aggregation:

from transformers import pipeline

model_id = "ivlcic/snerta-8l-base"
ner = pipeline(
    task="token-classification",
    model=model_id,
    tokenizer=model_id,
    aggregation_strategy="simple",
)

text = (
    "Janez Novak... Metka Kralj,,. in Boris A. Novak živijo v Ljubljani "
    "in delajo za Microsoft."
)

for entity in ner(text):
    span = text[entity["start"]:entity["end"]]
    print(entity["entity_group"], span, round(float(entity["score"]), 3))

The example identifies Janez Novak, Metka Kralj, and Boris A. Novak as PER, Ljubljani as LOC, and Microsoft as ORG.

For applications that need to preserve an existing tokenisation—including whitespace and punctuation—the model can also be called with pre-split tokens, as in the CaNNopy inference example:

import re

tokens = re.findall(r"\s+|\w+|[^\w\s]", text, flags=re.UNICODE)
entities = ner(
    tokens,
    is_split_into_words=True,
    delimiter="",
)[0]

for entity in entities:
    span = text[entity["start"]:entity["end"]]
    print(entity["entity_group"], span)

Inputs longer than 256 model tokens should be split into overlapping windows by the application. Take care to reconcile entities that cross window boundaries.

Training data

The training corpus and its derived splits are not distributed with this model or in the supplementary repository. Obtain each source corpus from its original provider and follow its license or access terms. For this model, source corpora belonging to the same language key were pooled before an 80/10/10 sentence-level train/validation/test split.

LanguageCodeSource corpus or corporaPrepared sentences before splitting and deduplicationRole in the paper
BulgarianbgBSNLP / SlavNER18,333Main
CzechcsBSNLP / SlavNER; CNEC 2.020,864Main
Croatianhrhr500k 1.024,794Main
PolishplBSNLP / SlavNER20,423Main
RussianruBSNLP / SlavNER25,141Main
SloveneslBSNLP / SlavNER; ssj500k 2.3, ELEXIS-WSD 1.0, and SentiCoref 1.0 from SUK 1.048,701Main
SerbiansrSETimes.SR 1.03,891Main
UkrainianukBSNLP / SlavNER; NER-UK 2.024,424Main

The checkpoint uses the full, unbalanced training pool for these eight language keys. It was not trained on the auxiliary WikiANN / PAN-X pools for Bosnian, Macedonian, Slovak, or Albanian. The separate Croatian WikiANN data key used for the paper's source-quality ablation was also not used.

After deduplication, the model's eight-language pool contains 137,009 training sentences, 18,030 validation sentences, and 18,414 test sentences. The training split contains approximately 2.78 million word-level tokens. The training pipeline labels only the first model subtoken of each original word and ignores later subtokens when computing the loss and metrics.

Deduplication and relationship to prior work

Unlike the precursor ivlcic/sour-sarma, this model was trained on sentence-deduplicated data. Duplicate matching was performed independently within each language data key on the NFKC-normalized, case-folded token sequence. When a duplicate crossed splits, the test occurrence was retained over validation and training, and validation was retained over training. Repetitions within a split were also removed.

Across the eight language keys used for this checkpoint, 13,118 of 186,571 prepared sentence instances were removed. Deduplication prevents exact sentence leakage but does not remove paraphrases, near-duplicates, or related sentences from the same document.

There is also an intentional label-space difference from the paper experiments. The controlled experiments in the paper use only PER, LOC, and ORG, mapping unsupported labels—including MISC—to O. This release retains MISC because it is intended for a broader operational usage scenario. Consequently, the benchmark below should not be compared directly with the paper's three-type, eight-evaluation-language, three-seed macro averages.

Source data terms

The combined training corpus does not have a single uniform data license. Each source retains its own license, access conditions, and citation requirements:

This section documents training-data provenance; it does not grant access to or permission to redistribute any source corpus. The Apache-2.0 license in this model repository applies to the model release and does not replace source-dataset terms.

Training procedure

The model was initialised from microsoft/mdeberta-v3-base and trained in FP32 with the following configuration:

HyperparameterValue
Maximum sequence length256
Epochs20
Per-device training batch size16
Gradient accumulation steps2
Effective training batch size32
Per-device evaluation batch size32
OptimizerPyTorch AdamW
Learning rate2e-5
Learning-rate scheduleLinear
Warmup ratio0.06
Weight decay0.01
Maximum gradient norm1.0
Dropout0.10
Random seed2611
Checkpoint selectionBest validation entity-level F1

The run evaluated and saved a checkpoint after every epoch. The selected checkpoint was from epoch 15, with validation F1 92.39. Training completed 85,620 optimiser steps; the recorded training runtime was approximately 4 hours 21 minutes. The run used PyTorch 2.11.0, Transformers 5.8.0, and seqeval 1.2.2.

The learning rate and dropout follow the mDeBERTa-v3 setting selected by the paper's bounded validation sweep. In the Transformers mDeBERTa implementation, the configured dropout maps to hidden dropout and therefore affects the encoder layers as well as the token-classification head.

Evaluation

The released checkpoint was evaluated once on the combined deduplicated test split for the same eight language keys used in training. Metrics were computed with seqeval at entity level: a prediction is correct only when both its span and entity type match exactly. Precision, recall, and F1 below are micro-averaged over entities; accuracy is calculated over labeled word positions.

Entity typePrecisionRecallF1
Overall91.8092.8292.31
LOC95.0796.0095.53
MISC84.1083.7983.95
ORG89.8492.3291.06
PER93.6293.9593.79

Token accuracy is 98.78% and test loss is 0.0917. These values come from the saved CaNNopy evaluation artefact for this checkpoint.

Limitations and biases

  • The benchmark uses a random sentence-level split of pooled source corpora. It does not measure cross-document, temporal, topical, or cross-domain generalisation.
  • Results come from one training seed and are aggregated across all eight languages. Performance can vary substantially by language and domain, and the aggregate score can obscure lower-performing subsets.
  • The corpora differ in domain, segmentation, annotation density, provenance, and label definitions. MISC is especially heterogeneous across sources.
  • The full-pool training recipe is intentionally unbalanced, so larger language corpora contribute more training examples.
  • Exact sentence deduplication does not remove near-duplicates or guarantee document-level separation.
  • Names, organisations, locations, and demographic groups that are rare or absent in the training corpora may be recognised less reliably. False positives and false negatives should be expected.
  • Although the base encoder is multilingual, this fine-tuned model was trained and evaluated only on the eight listed languages. Performance on other languages is unknown.
  • Sequences are truncated at 256 model tokens unless the calling application implements windowing.

Reproducibility

Как запустить

На своей GPU в ailist. Цена — по текущим предложениям провайдеров

GPU в ailist

Универсальный рантайм · transformers · token-classification

Можно запустить

Подбираем GPU…

Класс архитектуры
DebertaV2ForTokenClassification
Ревизия весов
43182f1

0 моделей