Downloads · 30 days
3
4% of all-time downloads
vidhyakshayakannan/appointment-intent-llama32-1b-sft
appointment-intent-llama32-1b-sft is a text generation model from vidhyakshayakannan. Use it when you need the model to write or continue text. It is set up for transformers.
This repository contains the merged Hugging Face Transformers model for a fine-tuned Llama 3.2 1B Instruct appointment intent classifier.
Downloads · 30 days
3
4% of all-time downloads
All-time downloads
74
Public
Parameters
1.2B
2.5 GB on disk
Likes
0
Public
Click a slice to open those files.
.safetensors2.5 GB · 99%
From the Hugging Face model README
This repository contains the merged Hugging Face Transformers model for a fine-tuned Llama 3.2 1B Instruct appointment intent classifier.
For local Ollama usage, use the GGUF repository:
https://huggingface.co/vidhyakshayakannan/appointment-intent-llama32-1b-sft-GGUF
The model classifies user messages sent to a scheduling assistant. It returns one intent label that a downstream scheduling agent can use to choose the next workflow.
Example:
User message:
Can you cancel my appointment tomorrow?
Model output:
CANCEL_APPOINTMENTS
This type of model is useful as a routing layer in an agentic application. Instead of asking a general LLM to complete the entire task in one step, the application can first classify intent, then call the right scheduling tool or API.
LIST_APPOINTMENTS
CANCEL_APPOINTMENTS
RESCHEDULE_APPOINTMENTS
UNSUPPORTED_REQUEST
BLOCK_SLOTS
UNBLOCK_SLOTS
UPDATE_SPECIAL_SLOTS
CONVERSATIONAL_GREETING
CLOSING_CONVERSATION
The fine-tuning notebook follows this process:
USER_INPUT and TARGET_INTENT values by stripping extra whitespace.meta-llama/Llama-3.2-1B-Instruct model to establish baseline accuracy and F1.system: intent-classification instructions
user: the scheduling message
assistant: the correct intent label
meta-llama/Llama-3.2-1B-Instructvidhyakshayakannan/appointment-intent-llama32-1b-sft-GGUFThe dataset contains 301 labeled examples with:
TEST_IDUSER_INPUTTARGET_INTENTThe fine-tuning run used an 80/20 stratified split: 240 training examples and 61 held-out test examples.
Class distribution:
| Intent | Examples |
|---|---|
BLOCK_SLOTS | 61 |
RESCHEDULE_APPOINTMENTS | 51 |
LIST_APPOINTMENTS | 46 |
UNBLOCK_SLOTS | 39 |
UPDATE_SPECIAL_SLOTS | 35 |
CANCEL_APPOINTMENTS | 32 |
UNSUPPORTED_REQUEST | 25 |
CONVERSATIONAL_GREETING | 6 |
CLOSING_CONVERSATION | 6 |
Held-out test results from the fine-tuning notebook:
| Model | Test Accuracy | Macro F1 | Weighted F1 |
|---|---|---|---|
| Base Llama 3.2 1B Instruct | 39.3% | 0.1753 | 0.3134 |
| Fine-tuned model | 85.2% | 0.8784 | 0.8549 |
The fine-tuned model substantially improves over the base model for this intent-classification task. A production system should validate the classifier with a larger dataset that reflects real scheduling traffic.
The model expects a chat-style prompt with a system instruction that asks it to return exactly one intent label.
System instruction:
You are an intent classifier for a doctor appointment booking system.
Classify the user message into exactly one of these following intents:
LIST_APPOINTMENTS, CANCEL_APPOINTMENTS, RESCHEDULE_APPOINTMENTS, UNSUPPORTED_REQUEST, BLOCK_SLOTS, UNBLOCK_SLOTS, UPDATE_SPECIAL_SLOTS, CONVERSATIONAL_GREETING, CLOSING_CONVERSATION
Reply with ONLY the EXACT intent label. Nothing else.
User message:
I need to move my appointment from Monday to Friday.
Expected output:
RESCHEDULE_APPOINTMENTS
For local Ollama usage, use the GGUF repo:
ollama pull hf.co/vidhyakshayakannan/appointment-intent-llama32-1b-sft-GGUF:Q4_K_M
curl -L https://huggingface.co/vidhyakshayakannan/appointment-intent-llama32-1b-sft-GGUF/resolve/main/Modelfile -o Modelfile
ollama create appointment-intent-sft -f Modelfile
ollama run appointment-intent-sft "I need to move my appointment from Monday to Friday."
Expected output:
RESCHEDULE_APPOINTMENTS
Use this model as the intent-routing layer:
UNSUPPORTED_REQUEST or ambiguous messages.This is a compact model trained on a small labeled dataset for a narrow scheduling-intent task. It is not a medical assistant and should not provide medical advice. Production deployment should include a larger dataset, stronger evaluation, monitoring, and fallback handling for ambiguous or unsupported requests.