Prompt Details
Model
(claude-5-5-sonnet)
Token size
1,628
Example input
[POSITIVE_CLASS_DEFINITION]: URGENT if a support ticket describes an active production outage, confirmed security breach, data loss, or imminent data-loss risk affecting multiple users and requiring action within hours. Emotional language, capitalization, and requests for faster service do not qualify.
[LABEL_NAMES]: URGENT / NOT URGENT
[ITEMS]: U01 | Checkout fails for all customers after deployment. U02 | Please change the address on my invoice. U03 | URGENT! The dashboard font looks strange. U04 | Nightly backups failed for three consecutive days. U05 | Users across three offices cannot sign in. U06 | I need my subscription canceled today. U07 | Customer records are visible to other accounts. U08 | A beta tester reports an occasional animation glitch. U09 | Payment processing fails for 40% of transactions. U10 | Please add a dark mode option. U11 | Database storage is almost full and still growing. U12 | The mobile app crashes for one customer.
Example output
**Items received:** 12. This is under 30, so every figure in later stages is indicative only. No predictions were sent with the items, so the blind condition holds.
**Decision rule:** Positive (URGENT) if the ticket describes an active production outage, a confirmed security breach, data loss, or an imminent data-loss risk, affecting more than one user and needing action within hours. Negative (NOT URGENT) otherwise.
Inferred exclusions:
1. Issues affecting a single user are not urgent.
2. Cosmetic issues, feature requests and routine account or billing changes are not urgent.
3. Deadlines or urgency stated by the requester ("today", "URGENT!") do not count.
Open points:
- Whether a repeated backup failure counts as an imminent data-loss risk when the ticket gives no timeframe.
- Whether a capacity warning counts when the ticket gives no growth rate or time to full.
| ID | My label | Confidence | Reason |
|---|---|---|---|
| U01 | URGENT | High | Checkout outage for all customers |
| U02 | NOT URGENT | High | Routine billing change |
| U03 | NOT URGENT | High | Cosmetic issue; urgent wording excluded |
| U04 | URGENT | Low | Three days of backup failures; data-loss risk |
| U05 | URGENT | High | Sign-in outage across three offices |
| U06 | NOT URGENT | High | Request for speed, no outage |
| U07 | URGENT | High | Cross-account data exposure, multiple accounts |
| U08 | NOT URGENT | High | Occasional glitch, one tester |
| U09 | URGENT | High | 40% of payments failing |
| U10 | NOT URGENT | High | Feature request |
| U11 | URGENT | Low | Storage nearly full and growing; no timeframe |
| U12 | NOT URGENT | High | Affects only one customer |
**Definition gaps:**
- U04: the definition does not say whether repeated backup failures with no stated timeframe count as imminent data-loss risk. I labeled it URGENT because it is a multi-day gap in backups.
- U11: the ticket gives no growth rate or time to full, so I cannot tell whether action is needed within hours. I labeled it URGENT because "almost full and still growing" implies near-term outage or data-loss risk.
Labels frozen. Send predictions as: ID | prediction
Instant access
Commercial use
Money‑backBy purchasing this prompt, you agree to our terms of service
5.0
1 review
30
Views
CLAUDE-5-5-SONNET
This prompt makes the model an independent second rater and runs a three-step audit:
✅ Labels your items blind against your own class definition, with a written decision rule and a list of definition gaps ✅ Builds the 2x2 agreement table and Cohen's kappa against your classifier's predictions ✅ Sends you only the contested items plus a small audit sample to adjudicate ✅ Estimates precision, recall, specificity, F1 and MCC for the full set from your adjudications
...more
Added 11 hours ago
- Reviews for this prompt (1)