Custom named-entity extractor
Extract your domain's entities (SKUs, gene names, ticket IDs…) with a private Llama-3.1-8B LoRA — no off-the-shelf NER fits your schema.
Dataset format: JSONL (instruct) — {text → [{type, span}]}
The flow
An interactive miniature of the actual training screen — step through it.
New training job
Fine-tune an open model on your data. GPU auto-selected by model size.
Detected: JSONL (instruct) · 52,002 rows · validated
Summary
Llama, Qwen3, Gemma, Mistral… VRAM estimated per method, GPU auto-selected.
Step by step
- 1
Prepare your dataset
Format ~200–2,000 examples as (text → tagged entity spans) pairs for your entity types. Quality over quantity — a few hundred clean rows beats tens of thousands of noisy ones. Upload it, or point at a HuggingFace dataset.
- 2
Pick the base model
Choose the recommended base below (or any HF repo id). The dashboard auto-selects a right-sized GPU; you can override it.
- 3
Configure the fine-tune
Rank 16, 3 epochs. Completions-only loss on the JSON span list keeps extraction tight.
- 4
Train
Fast fine-tuning finishes in minutes. You get a standard safetensors adapter and a fit-quality receipt.
- 5
Deploy & serve
One click deploys your adapter onto a shared base-model GPU and gives you an OpenAI-compatible endpoint. You pay per token, not per idle GPU-hour. Swap one base_url and you're live.
Build the information extraction model
Standard safetensors out, OpenAI-compatible endpoint in. Export anytime — your weights are yours.