Instructions to use Qwen/Qwen2.5-1.5B-Instruct with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use Qwen/Qwen2.5-1.5B-Instruct with Transformers:
# Use a pipeline as a high-level helper from transformers import pipeline pipe = pipeline("text-generation", model="Qwen/Qwen2.5-1.5B-Instruct") messages = [ {"role": "user", "content": "Who are you?"}, ] pipe(messages)# pip install -U transformers accelerate # Load model directly from transformers import AutoTokenizer, AutoModelForCausalLM tokenizer = AutoTokenizer.from_pretrained("Qwen/Qwen2.5-1.5B-Instruct") model = AutoModelForCausalLM.from_pretrained("Qwen/Qwen2.5-1.5B-Instruct", device_map="auto") messages = [ {"role": "user", "content": "Who are you?"}, ] inputs = tokenizer.apply_chat_template( messages, add_generation_prompt=True, tokenize=True, return_dict=True, return_tensors="pt", ).to(model.device) outputs = model.generate(**inputs, max_new_tokens=256) print(tokenizer.decode(outputs[0][inputs["input_ids"].shape[-1]:])) - Inference
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- vLLM
How to use Qwen/Qwen2.5-1.5B-Instruct with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "Qwen/Qwen2.5-1.5B-Instruct" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "Qwen/Qwen2.5-1.5B-Instruct", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/Qwen/Qwen2.5-1.5B-Instruct
- SGLang
How to use Qwen/Qwen2.5-1.5B-Instruct with SGLang:
Install from pip and serve model
# Install SGLang from pip: pip install sglang # Start the SGLang server: python3 -m sglang.launch_server \ --model-path "Qwen/Qwen2.5-1.5B-Instruct" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "Qwen/Qwen2.5-1.5B-Instruct", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker images
docker run --gpus all \ --shm-size 32g \ -p 30000:30000 \ -v ~/.cache/huggingface:/root/.cache/huggingface \ --env "HF_TOKEN=<secret>" \ --ipc=host \ lmsysorg/sglang:latest \ python3 -m sglang.launch_server \ --model-path "Qwen/Qwen2.5-1.5B-Instruct" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "Qwen/Qwen2.5-1.5B-Instruct", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }' - Docker Model Runner
How to use Qwen/Qwen2.5-1.5B-Instruct with Docker Model Runner:
docker model run hf.co/Qwen/Qwen2.5-1.5B-Instruct
Fine-tune for Indian address parsing to structured JSON
I fine-tuned Qwen2.5-1.5B-Instruct (LoRA, merged) to parse messy Indian addresses into JSON (flat, building, street, landmark, area, city, state, pincode, phone).
On a held-out synthetic test set (500 addresses), full-record exact match went from 1.4% (base) to 98.0%.
Note: results are on synthetic data only; real-world accuracy is not yet measured.
Model: https://huggingface.co/abr-6024/indian-address-parser-1.5B
Dataset + generator: https://huggingface.co/datasets/abr-6024/indian-address-parsing-synthetic
Thanks to the Qwen team for the base model. Feedback and real-address test data welcome.
Update: v3 is now the main version of this model, and please disregard the 98.0% figure above.
That 98.0% was measured on synthetic text only, and it did not hold up on addresses I wrote by hand (about 58% on a stress set). v3 is trained on addresses whose locality, pincode, district and state come from the India Post pincode directory (Tamil Nadu is 44% of the data).
Results for v3:
- Held-out synthetic test (800 addresses): 94.4% full-record exact match; 93.0% on six districts never seen in training
- Hand-written Tamil Nadu set: 29/30 (written by me with the generator's conventions, so not an independent benchmark)
- Hand-written mixed-India set: 80.6% (part of the gap is that v3 uses city = district)
- Not measured on real customer addresses yet, so expect lower accuracy there
Model: https://huggingface.co/abr-6024/indian-address-parser-1.5B
Dataset + generator: https://huggingface.co/datasets/abr-6024/indian-address-parsing-synthetic
Anonymized real-address test cases, or feedback on the conventions, are welcome.