---
title: "Comment by Neurobro on \"Teaching a Small Language Model to Triage Incidents: A Beginner’s Unsloth and QLoRA Tutorial\" | Hashnode"
description: "The split where 2 scenarios went 0/8 on category and the other 3 went 8/8 is the most interesting part to me. Feels less like a weak model and more like it latc"
url: "https://hashnode.com/posts/teaching-a-small-language-model-to-triage-incidents-a-beginner-s-unsloth-and-qlora-tutorial/6ae3e635d6f91c173574e3a9/comment/6ae45e90ad61bfcfec09bd47"
---

[Discussion](https://hashnode.com/posts/teaching-a-small-language-model-to-triage-incidents-a-beginner-s-unsloth-and-qlora-tutorial/6ae3e635d6f91c173574e3a9)

Comment [Teaching a Small Language Model to Triage Incidents: A Beginner’s Unsloth and QLoRA Tutorial](https://hashnode.com/posts/teaching-a-small-language-model-to-triage-incidents-a-beginner-s-unsloth-and-qlora-tutorial/6ae3e635d6f91c173574e3a9)

[Neurobro](https://hashnode.com/@neurobro)

[Oct 30](https://hashnode.com/posts/teaching-a-small-language-model-to-triage-incidents-a-beginner-s-unsloth-and-qlora-tutorial/6ae3e635d6f91c173574e3a9/comment/6ae45e90ad61bfcfec09bd47)

The split where 2 scenarios went 0/8 on category and the other 3 went 8/8 is the most interesting part to me. Feels less like a weak model and more like it latched onto surface words - a signing-key "rotation" reads a lot like a deploy. Would be curious if human-written paraphrases of those two flip the numbers. Also respect for counting fenced JSON as a hard fail instead of quietly repairing it.

[Haithem Slimi](https://hashnode.com/@haithem-slimi)

[Oct 30](https://hashnode.com/posts/teaching-a-small-language-model-to-triage-incidents-a-beginner-s-unsloth-and-qlora-tutorial/6ae3e635d6f91c173574e3a9/comment/6ae45e90ad61bfcfec09bd47#reply-6ae4fd84ceb94a7055ae95fa)

That’s a plausible hypothesis, although the aggregate results alone don’t establish it. I’d need to inspect the raw predictions and compare the misleading cues across examples.

Human-written paraphrases would be a good follow-up: keep the same labels and held-out scenarios, remove some of the obvious lexical cues, and evaluate the same adapter without retraining. That would help distinguish scenario understanding from keyword matching.

And yes, fenced JSON was intentionally a hard failure because the output was defined as a strict application interface rather than text to be repaired silently.
