#sentiment annotation

Conversational AI systems chatbots, virtual assistants, voice-enabled applications need to understand two things about every user input: what the user is trying to accomplish (intent) and how they feel about it (sentiment). These are not the same task, they are not measured the same way, and they are not equally difficult to annotate correctly.

Intent annotation and sentiment annotation are among the highest-volume text annotation tasks in production NLP development. They are also among the most taxonomy-dependent: the quality of the annotation is bounded by the quality of the taxonomy design, and taxonomy problems that seem minor at the design stage compound into significant model accuracy problems at scale.

Intent Annotation: What It Is and Where It Fails

Intent annotation classifies an utterance by what the user is trying to accomplish. A user message like "Can you tell me my account balance?" has the intent "check_account_balance." A message like "I want to cancel my subscription" has the intent "cancel_subscription." The intent classifier trained on annotated examples learns to route new messages to the correct intent.

The quality of intent annotation depends almost entirely on the quality of the intent taxonomy the defined set of intents and their boundaries and the quality of the boundary examples provided to annotators.

The Taxonomy Design Problem

Intent taxonomies designed by product teams rather than annotation linguists consistently have the same problems:

Overly broad intents that collapse genuinely different user goals: "Account help" might be intended to cover account balance inquiries, account history requests, account number inquiries, and account security questions. These are four different user goals that might route to four different system responses. Collapsing them into one intent hides this routing information from the model.

Overly narrow intents that fragment synonymous user expressions: Creating separate intents for "check balance," "what's my balance," and "balance inquiry" when all three should route to the same system response adds annotation complexity without adding meaningful routing information.

Missing intents that leave common user expressions without a matching category: When user utterances arrive that don't fit any defined intent, annotators apply the closest available category — producing misclassified training examples that teach the model to map those utterances to the wrong intent.

Unclear intent boundaries that produce annotator disagreement: When two intents are closely related "upgrade_plan" and "change_plan" annotators make different decisions about which to apply to ambiguous utterances like "I want to move to a different tier." High IAA on unambiguous utterances masks the low agreement on the boundary cases that determine model accuracy in real deployment.

The Out-of-Scope Category

Every intent taxonomy needs an explicit out-of-scope (OOS) category for utterances that don't map to any defined intent. Without an OOS category, annotators force out-of-scope utterances into the closest available intent producing training data that teaches the model to confidently misclassify inputs that should trigger a graceful fallback response.

OOS annotation requires annotators to resist the temptation to find a plausible-seeming intent for every utterance. An utterance that is genuinely out of scope should be labeled OOS, even if a creative interpretation could map it to an existing intent. Guidelines that provide examples of utterances that should be labeled OOS, alongside the reasoning for why they don't fit any defined intent, calibrate annotators toward correct OOS labeling.

Multi-Intent Utterances

Users sometimes express multiple intents in a single message: "Can you check my balance and also help me update my address?" Both "check_account_balance" and "update_address" are expressed in one utterance. Single-label intent annotation forces the annotator to choose one primary intent, discarding the information about the secondary intent.

Multi-intent annotation programs support labeling all intents expressed in a single utterance, with a primary/secondary designation where one intent is more focal. This produces training data that enables intent classifiers that detect multiple concurrent intents rather than requiring users to express one goal at a time.

Sentiment Annotation: Granularity Determines Usefulness

Sentiment annotation is the most commonly simplified text annotation task in NLP development and the most commonly regretted simplification. Three-class sentiment (positive, negative, neutral) is fast to annotate and produces models that are easy to evaluate. It is also coarse enough to be commercially useless for most applications that require nuanced sentiment understanding.

The Granularity Decision

Three-class sentiment (positive / negative / neutral): Appropriate for applications that need a basic valence signal is this customer review favorable or unfavorable? but insufficient for applications that need to act on the specific type and intensity of sentiment expressed.

Five-class sentiment (strongly positive / slightly positive / neutral / slightly negative / strongly negative): Adds intensity to the valence signal. Useful for ranking rather than just classifying: identifying the most negative customer feedback for priority escalation, or the most positive reviews for promotional content.

Aspect-based sentiment (sentiment per aspect): Rather than assigning a single sentiment to a document, aspect-based annotation labels the sentiment expressed toward each mentioned aspect of the product or service. A hotel review might be positive about the location, negative about the service, and neutral about the price. Aspect-based annotation produces models that support actionable feedback analysis identifying which specific product dimensions are driving negative sentiment.

Fine-grained emotion annotation: Beyond valence and intensity, fine-grained emotion annotation labels the specific emotional state expressed frustration, satisfaction, confusion, disappointment, delight. Fine-grained emotion models support sentiment-aware dialogue systems that adapt their responses to the user's emotional state rather than only to the polarity of their sentiment.

For customer service AI applications where the system needs to prioritize escalations, adapt response tone, and identify coaching opportunities from agent-customer interactions, fine-grained emotion annotation consistently produces more valuable models than three-class sentiment.

The Ambiguity Problem in Sentiment Annotation

Sentiment annotation has genuinely high inherent ambiguity in the edge cases that appear most frequently in real customer communications. Sarcasm that should be negative is expressed in surface-positive language. Mild criticism is expressed in diplomatic language that reads as neutral or slightly positive. Cultural and individual variation in expression means the same sentiment may be expressed with different language markers across different demographic groups.

IAA for sentiment annotation on genuinely ambiguous utterances reflects this: inter-annotator agreement for three-class sentiment on non-obvious examples is typically lower than for most other annotation tasks, with Cohen's Kappa often in the 0.65–0.75 range for the hard cases even among calibrated annotators.

The production annotation response to this inherent ambiguity is to explicitly label ambiguous examples as uncertain using a separate "ambiguous" category or a confidence weight rather than forcing a hard label. Models trained with explicit ambiguity labels develop calibrated uncertainty rather than overconfident predictions on the hard cases.

Irony, Negation, and Context Dependency

Sentiment annotation requires understanding constructs that surface-pattern matching cannot handle:

Irony and sarcasm: "Oh great, another hour on hold" is expressed in nominally positive language but carries negative sentiment. Identifying irony requires understanding the pragmatic context the topic being discussed, the relationship between the surface language and the expected reaction that requires annotators with cultural and contextual knowledge.

Negation scope: "I don't like the product but the service was excellent" contains both positive and negative sentiment in the same sentence, with "not" scoping over "like" to invert its sentiment polarity. Annotation guidelines need to specify how negation is handled: whether the negated sentiment is labeled with the inverted polarity, labeled as neutral, or labeled with an explicit negation marker.

Context-dependent sentiment: "The wait time was three hours" carries negative sentiment in a restaurant review context and no particular sentiment in a hospital emergency context where wait time expectations are different. Annotators need access to sufficient context to correctly interpret sentiment-relevant expressions.

LLM Alignment Annotation: Where Intent and Sentiment Meet RLHF

The latest generation of text annotation for conversational AI involves a distinct task type: annotating AI model outputs for quality, helpfulness, and safety rather than annotating user inputs for intent and sentiment.

This annotation used in RLHF (Reinforcement Learning from Human Feedback) and preference optimization for LLMs asks annotators to evaluate and rank AI-generated responses to prompts. The quality dimensions being evaluated are:

Helpfulness: Does the response address what the user actually needed? Does it provide accurate, complete, and actionable information?

Accuracy: Are the claims in the response factually correct? Can the annotator verify the claims against reliable sources?

Safety: Does the response avoid harmful content, inappropriate recommendations, or privacy violations?

Tone and appropriateness: Is the response's tone appropriate for the context? Is it appropriately formal or conversational? Does it show appropriate acknowledgment of sentiment expressed in the user's message?

Annotating LLM response quality requires annotators with significantly more sophisticated judgment than standard intent or sentiment annotation they need to evaluate the AI's response against their own understanding of what a correct, helpful, and safe response looks like. Domain expertise is critical: annotators evaluating medical AI responses need sufficient medical knowledge to assess whether the response is medically accurate.

Final Thought

Intent and sentiment annotation are the text annotation tasks that most directly determine conversational AI capability. Taxonomy quality, boundary clarity, granularity decisions, and handling of the hard cases sarcasm, negation, ambiguity, multi-intent utterances together determine whether the annotated training data produces a conversational AI that understands what users need and how they feel.