anonym.legal

By · Last updated 2026-02-26

Nazaj na blogTehnično

Vecjezicni NER: angleski modeli odpadejo pri arabscini

Modeli NER, usposobljeni na anglescini, dosegajo natancnost 85-92 %. Arabscina in kitajscina? Pogosto 50-70 %. Spoznajte tehnicne izzive in kako graditi prave resitve.

February 26, 20268 min branja
NERmultilingualArabic NLPChinese NLPPII detection

Vecjezicni NER: Izzivi pri zaznavanju PII

Posodobljeno za leto 2026

Vrzel v natancnosti

Modeli NER, usposobljeni na anglescini, dosegajo 85-92 % F1 na standardnih testih. Aplicirajte iste modele na arabsko ali kitajsko besedilo. Natancnost pade na 50-70 %.

Za delo s PII je ta vrzel problem. 70-odstotna stopnja zadetkov pomeni, da 30 % obcutljivih podatkov ostane neopazenih.

Vzroki niso napake. Izhajajo iz razlik v pisnih sistemih.

Stiri temeljni vzroki

1. Meje besed

Anglescina loci besede s presledki. Tokenizacija je enostavna.

Kitajscina nima presledkov sploh.

"Zhangwei zhu zai Beijing"
-> Najprej razdeli: ["Zhang Wei", "zhu zai", "Beijing"]

Model ne more oznaciti tistega, cesar ne najde. Delitev mora priti pred NER.

Arabski crkovnik znotraj besed. Kratki samoglasniki so izpusceni. Besedilo tece od desne proti levi.

"Muhammad ya'ish fi Dubai"
-> Brez kratkih samoglasnikov, desno-levo, vezani crkovniki

2. Morfologija

Angleske glagolske oblike se spremenijo na malo nacinov. Arabscina uporablja korenski sistem. En koren ustvari ducate besed.

k-t-b ("pisati")
-> katib (pisec), kitab (knjiga), maktaba (knjiznica)

NER mora razcleniti korene, da najde imena v izpeljanih oblikah besed.

3. Konvencije imen

Latinska imena gredo Ime potem Priimek. Imena v jezikih od desne proti levi verigenj druzinskih vez.

Muhammad ibn Abd Allah
(Muhammad sin Abdullaha)

Kitajska imena postavljajo druzinsko ime na prvo mesto. Vecina imen je dolga dva ali tri znake.

Zhang Wei - 2 znaka
Ouyang Xiu - 3 znaki

Model, zgrajen na zahodnih vzorcih imen, bo te strukture zamudil.

4. Smer besedila

Nekateri jeziki tecejo od desne proti levi. Ko besedilo RTL vsebuje anglesko ime, se vizualni in logicni red locita. To se imenuje besedilo BiDi. Zahteva skrbno razclenjievanje.

Vrednosti F1 po pisnih sistemih

JezikPisni sistemRazpon F1Stopnja
AnglescinaLatinica85-92 %Nizka
NemscinaLatinica82-88 %Nizka
Francos cinaLatinica80-87 %Nizka
SpanscinaLatinica81-86 %Nizka
RuscinaCirilica75-83 %Srednja
ArabscinaAbdzkad55-75 %Visoka
KitajscinaHanzi60-78 %Visoka
JaponscinaMesano65-80 %Visoka
TajscinaTajski50-70 %Zelo visoka
HindujscinaDevanagari60-75 %Visoka

Ne-latinski sistemi in manjkajoci presledki med besedami znizujejo rezultate.

Trostopenjska resitev

Uporabljamo tri stopnje za pokritost 48 jezikov in pisnih sistemov.

Stopnja 1: spaCy - 25 jezikov

Za jezike z mocnimi, preizkusenimi modeli. To pokriva anglescino, nemscino, francos cino, spanscino, italijan scino, portugals cino, nizozemscino, poljs cino, ruscino in grs cino.

Stopnja 2: Stanza - Zapleteni jeziki

Stanford Stanza obravnava arabscino, kitajscino, japonscino in korejscino. Izvaja delitve besed in analizo korenov pred NER.

Stopnja 3: XLM-RoBERTa - Jeziki z malo viri

Za jezike brez namenskin modelov. Sem gredo tajscina, vijetnamscina, hindujscina, bengalscina, hebrejscina, turscina in farscina. Obravnava mesano jezikovno besedilo brez eksplicitnih zastavic.

RTL in BiDi

Besedilo od desne proti levi potrebuje dodatne korake po delitvi.

Nas cevovod:

  1. Normalizira besedilo v logicni red.
  2. Zazene NER v tem redu.
  3. Preslika polozaje entitet nazaj v vizualni red.

Pred NER odstranimo pripete predpone in jih po tem dodamo nazaj.

"Muhammad" -- samo ime
"li-Muhammad" -- "Muhammadu" (predpona vkljucena)

Preklop kode

Pravi dokumenti pogosto mesajo jezike v eni vrstici.

"El meeting con John es at 3pm"
"Danes sem s Johnom sel shopping"

Nas cevovod razdeli po jeziku. Za vsak del zazene pravi model. Nato zdruzi rezultate s preslikavo polozajev.

Notranje primerjave

Rezultati iz notranjih testov na mesanojezikovnih podatkih:

ScenarijF1
Samo anglescina91 %
Samo nemscina88 %
Samo arabscina79 %
Samo kitajscina81 %
Mes. anglescina-arabscina83 %
Mes. anglescina-kitajscina84 %
Mes. anglescina-nemscina89 %

Opombe za namestitev

Namizna aplikacija samodejno zazna jezik po dokumentu. Za mesanojezikovne datoteke obdela vsak segment s pravim modelom. Nobenega roc nega koraka ni potrebno.

Nastavite jezik v API, ko ga poznate:

{
  "text": "Muhammad ibn Abd Allah",
  "language": "ar"
}

Uporabite samodejno zaznavanje, ko ga ne poznate:

{
  "text": "Muhammad ibn Abd Allah",
  "language": "auto"
}

Po meri vzorci morajo pokrivati lokalno specificne stevilke:

# Latinicna ID zaposlovalca
EMP-[0-9]{6}

# Arabska ID zaposlovalca (vkljucno z arabsko-indijskimi stevilkami)
Muwazzaf-[arabske-stevilke 0-9]{6}

Oglejte si celoten seznam entitet. Za nastavitev API obiscite stran funkcij API. Nas vodic za skladnost GDPR obravnava, kako vrzeli pri zaznavanju vplivajo na zakon o varstvu podatkov.


anonym.legal uporablja trostopenjski sklad NER - spaCy, Stanza in XLM-RoBERTa - za pokritost 48 jezikov z doslednim zaznavanjem PII.

Viri

Ste pripravljeni zaščititi svoje podatke?

Začnite z anonimizacijo PII z več kot 285 tipi entitet v 48 jezikih.

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

Related reading

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our servers live in Falkenstein, Germany.

We use Hetzner. They hold ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.