Instructions to use tkatz123/qwen2.5-3b-job-extraction-gguf with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use tkatz123/qwen2.5-3b-job-extraction-gguf with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M # Run inference directly in the terminal: llama cli -hf tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M # Run inference directly in the terminal: llama cli -hf tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M
Use pre-built binary
# Download pre-built binary from: # https://github.com/ggerganov/llama.cpp/releases # Start a local OpenAI-compatible server with a web UI: ./llama-server -hf tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M
Build from source code
git clone https://github.com/ggerganov/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-server llama-cli # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama-server -hf tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M
Use Docker
docker model run hf.co/tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M
- LM Studio
- Jan
- Ollama
How to use tkatz123/qwen2.5-3b-job-extraction-gguf with Ollama:
ollama run hf.co/tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M
- Unsloth Desktop
- Pi
How to use tkatz123/qwen2.5-3b-job-extraction-gguf with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M
Configure the model in Pi
# Install Pi: npm install -g @earendil-works/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "llama-cpp": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use tkatz123/qwen2.5-3b-job-extraction-gguf with Docker Model Runner:
docker model run hf.co/tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M
- Lemonade
How to use tkatz123/qwen2.5-3b-job-extraction-gguf with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M
Run and chat with the model
lemonade run user.qwen2.5-3b-job-extraction-gguf-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use tkatz123/qwen2.5-3b-job-extraction-gguf with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M
Configure Hermes
# Install Hermes: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash hermes setup # Point Hermes at the local server: hermes config set model.provider custom hermes config set model.base_url http://127.0.0.1:8080/v1 hermes config set model.default tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use tkatz123/qwen2.5-3b-job-extraction-gguf with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M
Configure OpenClaw
# Install OpenClaw: npm install -g openclaw@latest # Register the local server and set it as the default model: openclaw onboard --non-interactive --mode local \ --auth-choice custom-api-key \ --custom-base-url http://127.0.0.1:8080/v1 \ --custom-model-id "tkatz123/qwen2.5-3b-job-extraction-gguf:Q4_K_M" \ --custom-provider-id llama-cpp \ --custom-compatibility openai \ --custom-text-input \ --accept-risk \ --skip-health
Run OpenClaw
openclaw agent --local --agent main --message "Hello from Hugging Face"
Qwen2.5-3B Job-Extraction β Q4_K_M GGUF
A Qwen2.5-3B-Instruct model fine-tuned (QLoRA) for structured extraction from job postings: raw posting β JSON of {required_skills, tech_stack, seniority, avg_comp_range}. This repo holds the Q4_K_M GGUF quantization (~1.8 GB) for CPU serving via llama.cpp / llama-cpp-python.
Part of a portfolio MLOps project (fine-tune β containerize β deploy on AWS).
Related artifacts
- LoRA adapter:
tkatz123/qwen2.5-3b-job-extraction - Merged fp16 model:
tkatz123/qwen2.5-3b-job-extraction-merged - Quantized GGUF (this repo): built from the merged model with llama.cpp
convert_hf_to_gguf.py+llama-quantize(Q4_K_M).
Results β fine-tuned vs. same base model, zero-shot
Field-level accuracy on a held-out test set (29 postings), scored under identical greedy decoding:
| Field | Base (zero-shot) | Fine-tuned | Ξ |
|---|---|---|---|
| seniority | 0.72 | 0.76 | +0.03 |
| comp (Β±10%) | 0.86 | 0.97 | +0.10 |
| skills (set-F1) | 0.17 | 0.27 | +0.10 |
| tech_stack (set-F1) | 0.08 | 0.68 | +0.60 |
| valid-JSON rate | 1.00 | 1.00 | β |
The largest gain is tech_stack (0.08 β 0.68): fine-tuning taught the model to cleanly separate named technologies (Python, PyTorch, AWS, Docker) from general competencies.
Usage (llama-cpp-python)
from llama_cpp import Llama
llm = Llama.from_pretrained(
repo_id="tkatz123/qwen2.5-3b-job-extraction-gguf",
filename="qwen2.5-3b-job-extraction-Q4_K_M.gguf",
n_ctx=4096,
)
resp = llm.create_chat_completion(
messages=[
{"role": "system", "content": EXTRACTION_PROMPT}, # see project repo
{"role": "user", "content": job_description},
],
max_tokens=1024,
temperature=0.0, # greedy, matches evaluation
)
print(resp["choices"][0]["message"]["content"])
Output is a JSON object: {"required_skills": [...], "tech_stack": [...], "seniority": "...", "avg_comp_range": <int|null>}.
Serving notes
Served as a FastAPI + Docker microservice on an AWS EC2 Graviton instance. The Q4_K_M quant needs ~4 GB RAM to serve comfortably (on a 2 GB box the weights don't stay resident and inference becomes disk-bound).
- Downloads last month
- 1
4-bit