turkish pii detection needs about 1.0 GB of memory at Q8_0 (a 0.3 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 2 quants, from 0.3 GB (Q8_0) to 0.6 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 0.6 GB.
Turkish PII detection and masking model
This 270M‑parameter model detects and masks personally identifiable information in Turkish text. It accepts masking instructions and outputs transformed text. The model is available in GGUF format for local inference.
Good at
- PII detection in Turkish
- Instruction‑conditioned masking
- Offline inference with Ollama or llama.cpp
Limits
- No vision support
- Requires 8k context for full memory estimate
- License is gemma
Best for
- Masking support tickets
- Pre‑processing logs
- Preparing documents for LLMs
Who it’s for. Developers needing to anonymise Turkish text before sending it to other systems. Data‑privacy teams can use it to comply with KVKK regulations.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q8_0 | 0.3 GB | 1.0 GB | Fits | Get file → | |
| BF16 | 0.6 GB | 1.2 GB | Fits | Get file → |
For 8 GB VRAM, use Q8_0 (0.3 GB file, ~1 GB memory at 8k context). For 16 GB VRAM, BF16 (0.55 GB file, ~1.2 GB memory at 8k context) offers higher precision. Estimates are approximate.
What GPU do you need for turkish pii detection?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: the best quant that fits is BF16 (0.6 GB file, about 1.2 GB in use).
Which turkish pii detection quant should you choose?
Q8_0 (0.3 GB) is the middle option in this repository. Close to lossless. It costs roughly twice the memory of a 4-bit file, so it suits cases where you have plenty of VRAM.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about turkish pii detection
How much VRAM does turkish pii detection need?
About 1.0 GB at Q8_0 with an 8K context window. That is the 0.3 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run turkish pii detection on an 8 GB GPU?
Yes, with BF16: the 0.6 GB file needs about 1.2 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of turkish pii detection GGUF?
It depends on the quant: Q8_0 is 0.3 GB, BF16 is 0.6 GB.
What context length does turkish pii detection support?
The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 0.2 GB at 8K and 0.6 GB at 32K.
Where can I download turkish pii detection GGUF?
The files are on Hugging Face in the halilneed/turkish-pii-detection-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does turkish pii detection use?
Hugging Face lists the license as gemma. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run this model on 8 GB VRAM?
Yes, the Q8_0 quantization uses about 1 GB of VRAM at 8k context, fitting within an 8 GB budget.
Does the model support English text?
No, it is trained exclusively on Turkish data and designed for Turkish PII masking.
Is the model open source?
Yes, it is released under the gemma license and available on the Hugging Face repository.