Amey9766 commited on
Commit
5a24a4b
·
verified ·
1 Parent(s): 93c22ff

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +178 -1
README.md CHANGED
@@ -229,4 +229,181 @@ Meta AI for the LLaMA 3.2 base model
229
 
230
  Hugging Face ecosystem (Transformers, PEFT, TRL)
231
 
232
- Public hotel review datasets used for training
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
229
 
230
  Hugging Face ecosystem (Transformers, PEFT, TRL)
231
 
232
+ Public hotel review datasets used for training
233
+
234
+ If you want next-level polish, I can:
235
+
236
+ optimize tags + metadata for Hugging Face search
237
+
238
+ add visual badges (perplexity, domain, task)
239
+
240
+ write a short launch post for LinkedIn / X
241
+
242
+ Just tell me 👍
243
+
244
+ it is still looking weird
245
+
246
+ You’re right — what you have works, but Hugging Face renders Markdown very literally.
247
+ Right now your card looks like a wall of text because it’s missing clear hierarchy, spacing, bullets, and visual anchors.
248
+
249
+ Below is a clean, well-structured, Hugging Face–optimized model card that you can copy-paste directly into README.md.
250
+ It will render nicely with bold headings, bullets, code blocks, and emojis (used sparingly).
251
+
252
+ 🚀 LLaMA-3.2 Hotel Review Triage Model
253
+
254
+ Model ID: Amey9766/llama32-hotel-review-triage
255
+ Base Model: meta-llama/Llama-3.2-1B-Instruct
256
+ Author: Amey Tillu
257
+ Task: Hospitality Review Triage → Structured JSON Output
258
+ Perplexity (validation): 3.02
259
+
260
+ 🧠 What This Model Does
261
+
262
+ This model is fine-tuned to analyze hotel guest reviews and convert unstructured feedback into clean, machine-readable JSON suitable for:
263
+
264
+ Complaint routing
265
+
266
+ Guest experience analytics
267
+
268
+ Operational alerting
269
+
270
+ AI hotel agents
271
+
272
+ It is designed to behave as a deterministic triage system, not a conversational chatbot.
273
+
274
+ 📌 Core Capabilities
275
+
276
+ Identifies complaint category (e.g. cleanliness, staff, facilities)
277
+
278
+ Estimates severity level (low / medium / high)
279
+
280
+ Infers department ownership (housekeeping, front desk, maintenance)
281
+
282
+ Produces strict, valid JSON output
283
+
284
+ Handles both negative complaints and positive feedback
285
+
286
+ 🏨 Example Use Case
287
+
288
+ Input
289
+
290
+ The room was dirty and the AC didn’t work.
291
+
292
+
293
+ Output
294
+
295
+ {
296
+ "category": "room_maintenance",
297
+ "severity": "high",
298
+ "department": "engineering",
299
+ "sentiment": "negative",
300
+ "summary": "Guest reports cleanliness issues and malfunctioning air conditioning."
301
+ }
302
+
303
+ 🧪 How to Use
304
+ from transformers import AutoTokenizer, AutoModelForCausalLM
305
+
306
+ model_id = "Amey9766/llama32-hotel-review-triage"
307
+
308
+ tokenizer = AutoTokenizer.from_pretrained(model_id)
309
+ model = AutoModelForCausalLM.from_pretrained(
310
+ model_id,
311
+ device_map="auto"
312
+ )
313
+
314
+ prompt = tokenizer.apply_chat_template(
315
+ [
316
+ {
317
+ "role": "system",
318
+ "content": "You are a hospitality review triage assistant. Output ONLY valid JSON."
319
+ },
320
+ {
321
+ "role": "user",
322
+ "content": "The room was dirty and the AC didn’t work."
323
+ }
324
+ ],
325
+ tokenize=False
326
+ )
327
+
328
+ inputs = tokenizer(prompt, return_tensors="pt").to(model.device)
329
+ output = model.generate(**inputs, max_new_tokens=256)
330
+
331
+ print(tokenizer.decode(output[0], skip_special_tokens=True))
332
+
333
+ 📊 Training Details
334
+
335
+ Dataset: Public hotel review datasets (Hugging Face)
336
+
337
+ Total examples used: ~120,000
338
+
339
+ Train / Validation split: 90% / 10%
340
+
341
+ Sequence length: 512 tokens
342
+
343
+ Fine-tuning method: LoRA (PEFT)
344
+
345
+ Training hardware: NVIDIA A100
346
+
347
+ Training time: ~10 hours
348
+
349
+ Epochs: 3
350
+
351
+ 📈 Evaluation
352
+
353
+ Validation Perplexity: 3.02
354
+
355
+ Stable loss convergence
356
+
357
+ No observed mode collapse
358
+
359
+ Minor variance expected due to diverse review lengths and tone
360
+
361
+ ⚠️ Limitations
362
+
363
+ Not trained on live hotel policies or property-specific rules
364
+
365
+ Does not replace human judgment for legal or compensation decisions
366
+
367
+ Assumes English-language reviews
368
+
369
+ Output schema is opinionated and may require adaptation
370
+
371
+ 🔐 License
372
+
373
+ This model inherits the license of its base model:
374
+
375
+ LLaMA 3.2 License (Meta)
376
+
377
+ Please ensure compliance with the base model’s license when using or redistributing this model.
378
+
379
+ 📚 Citation
380
+
381
+ If you use this model in research or production systems, please cite:
382
+
383
+ @misc{tillu2026llama32hoteltriage,
384
+ title = {LLaMA-3.2 Hotel Review Triage Model},
385
+ author = {Amey Tillu},
386
+ year = {2026},
387
+ howpublished = {\url{https://huggingface.co/Amey9766/llama32-hotel-review-triage}},
388
+ note = {Fine-tuned on hospitality reviews for structured JSON triage}
389
+ }
390
+
391
+ 🙏 Acknowledgements
392
+
393
+ Meta AI for the LLaMA-3.2 base model
394
+
395
+ Hugging Face ecosystem (Transformers, PEFT, TRL)
396
+
397
+ Public hospitality review datasets used for training
398
+
399
+ ⭐ When to Use This Model
400
+
401
+ Use this model when you need:
402
+
403
+ Reliable structured outputs
404
+
405
+ Fast review triage
406
+
407
+ Integration into hotel operations pipelines
408
+
409
+ A foundation for AI hospitality agents