A large e-commerce company receives thousands of customer support emails daily. These emails need to be routed to the correct department: 'Billing', 'Technical Support', or 'Sales'. Manually sorting these emails is slow and inefficient. Analyze this business problem and describe how you would frame it as a natural language processing task. Your answer should identify the specific task and explain what key components would be required to build an automated solution.

Google

Text classification is one of the most prevalent tasks in Natural Language Processing (NLP). It involves the broad problem of assigning a given piece of text to one or more predefined labels or categories.

Text Classification in NLP

Polarity classification is a popular and well-defined text classification task within sentiment analysis. Its general objective is to categorize a given text into one of three sentiment categories: positive, negative, or neutral.

Polarity Classification

Although Large Language Models appear to be a direct solution for classification tasks, their application involves several unresolved challenges that have not been fully explored or solved.

Unaddressed Issues in LLM-based Classification

For complex classification problems where a sufficient amount of labeled data is available, alternatives to standard prompting are often preferable. These methods include fine-tuning a Large Language Model on the specific task or employing architectures that combine a pre-trained encoder with a classifier, such as the 'BERT + classifier' model.

Alternative Approaches for Difficult Classification Tasks

A technology news website wants to build a system to automatically sort its articles into a single, most relevant category for its main navigation menu. The goal is to ensure that readers can easily find articles on specific topics and that each article appears in only one section. Which of the following sets of predefined categories is best designed for this task?

Automating Customer Support Email Routing

Match each real-world scenario with the most appropriate text classification framework.

You lead an NLP team that must deploy a polarity classifier for customer feedback (labels: Positive, Negative, Neutral) into a regulated product where (a) outputs must be one of the three labels only (no extra text), (b) the system must be auditable and stable across weekly model updates, and (c) you have 8,000 labeled examples but also need a fast proof-of-value in 2 weeks.

Write a recommendation memo (as if to an engineering manager) that proposes an end-to-end approach and justifies it by explicitly comparing: (1) a single-text classifier built with a BERT-style encoder using the [CLS] representation plus a prediction head, versus (2) classification via prompt completion using a text-generation LLM.

Your memo must explain how you would ensure the final output is always one of {Positive, Negative, Neutral} in the prompt-completion approach (including a concrete label-mapping strategy and how you would handle non-literal outputs like “This review is mostly satisfied but with minor issues”), and how that requirement differs from the BERT approach. Conclude with the key tradeoffs you are accepting (time-to-ship, accuracy, auditability, and failure modes) and the conditions under which you would switch from one approach to the other after the initial launch.

Choosing and Operationalizing a Sentiment Classifier Under Real Production Constraints

You are launching a customer-feedback analytics feature that must assign exactly one sentiment label to each incoming message: {positive, negative, neutral}. You have two candidate implementations:

A) Fine-tune a BERT-style single-text classifier that uses the [CLS] representation and a softmax head to output class probabilities.

B) Use an LLM with classification via prompt completion (e.g., a cloze-like prompt that elicits a short completion), then apply a label-mapping layer that converts the model’s generated text into one of {positive, negative, neutral}.

In a 1–2 page response, recommend one approach for production and justify your choice by explicitly analyzing how (i) the nature of text classification and polarity classification, (ii) the mechanics of BERT single-text classification, and (iii) prompt-completion outputs plus label mapping interact to affect reliability and operational risk. Your answer must include: (1) a concrete example prompt you would use if you choose approach B (or explain why you would avoid B), (2) a proposed label-mapping strategy that handles both “direct label word” outputs (e.g., “negative”) and descriptive outputs (e.g., “This sounds frustrated with the service”), and (3) at least two failure modes unique to your non-chosen approach and how they would show up in real customer messages.

Designing a Robust Polarity Classifier: BERT vs Prompt-Completion and the Label-Mapping Contract

You are rolling out a polarity classification feature (labels: Positive, Negative, Neutral) for internal customer-feedback triage. To reduce risk, you run two models in parallel on the same incoming text: (1) a fine-tuned BERT single-text classifier that outputs a probability distribution over the three labels, and (2) an LLM prompt-completion approach where the prompt ends with a cue like "Overall sentiment:" and the model generates a short completion that your system maps to one of the three labels.

In a pilot, you observe a recurring failure mode: for many clearly negative comments (e.g., "The update broke my workflow and support hasn’t responded"), the LLM often completes with phrases like "not great" or "pretty disappointed" or even full sentences like "This sounds frustrating for the user," and your current label-mapping logic sometimes maps these to Neutral (because it only looks for exact label words). Meanwhile, BERT assigns high probability to Negative.

Write an essay that (a) diagnoses why this disagreement is happening in terms of how text classification differs between a BERT [CLS]-based classifier and classification via prompt completion, and (b) proposes a concrete, production-ready redesign of the prompt and the label-mapping contract that would reduce mis-mappings without sacrificing the ability to handle Neutral. Your answer must include: the exact revised prompt you would deploy, the mapping rules/algorithm you would implement (including how you handle outputs that do not contain any label word), and how you would use BERT’s probability output during rollout (e.g., gating, arbitration, or monitoring) to detect remaining mapping failures.

Debugging a Sentiment Pipeline: When Prompt-Completion and Label Mapping Disagree with a BERT Classifier

You own a production sentiment (polarity) classifier for customer chat transcripts with the required label set {positive, neutral, negative}. The current system is a fine-tuned BERT single-text classifier that takes one transcript at a time and outputs a probability distribution over the three labels. To reduce serving cost, a team proposes switching to an LLM using classification via prompt completion (text generation) and then mapping the generated text to one of the three labels.

After a pilot, you observe the following on the same 1,000 transcripts:
- BERT outputs are always one of {positive, neutral, negative}.
- The LLM often generates completions like: (a) "positive", (b) "mostly positive", (c) "mixed feelings", (d) "not great", (e) "the customer is satisfied overall", (f) "neutral/unclear".
- Your current label-mapping rule is: if the generated text contains the substring "positive" → positive; else if it contains "negative" or "not" → negative; else if it contains "neutral" → neutral; else → neutral.
- Business stakeholders report a spike in escalations because many "mixed feelings" and "neutral/unclear" cases are being treated as negative in downstream workflows.

As the responsible ML lead, propose a revised end-to-end classification design (prompt + label mapping approach, and whether/where you would keep or replace the BERT classifier) that reduces these misroutes while still meeting the requirement that the final output is exactly one of {positive, neutral, negative}. In your answer, explicitly explain how your design uses prompt-completion behavior and label mapping to control outputs, and how it compares to the BERT single-text classification approach in terms of reliability of label production.

Stabilizing a Polarity Classifier When Migrating from BERT to Prompt-Completion

You are rolling out a polarity (positive/negative/neutral) classifier for customer chat transcripts. For latency reasons, the product team wants to use a fine-tuned BERT single-text classifier in the primary path, but also wants an LLM prompt-completion fallback when the BERT model’s top probability is below 0.55. The analytics team requires that downstream dashboards see a single, consistent label set {positive, negative, neutral} regardless of which model produced the decision, and they will reject any output that cannot be deterministically mapped into exactly one of those three labels.

Unifying Sentiment Labels Across a BERT Classifier and a Prompt-Completion LLM

You are launching a company-wide “Voice of Customer” dashboard that must assign exactly one sentiment label (Positive, Negative, or Neutral) to each incoming customer comment within 200 ms. You have two models available behind a feature flag:

- Model A: a fine-tuned BERT single-text classifier that outputs a probability distribution over {Positive, Negative, Neutral}.
- Model B: a text-generation LLM used via prompt completion. The prompt ends with: “Sentiment (Positive/Negative/Neutral):” but the LLM sometimes returns variants like “mostly positive”, “not negative”, “mixed feelings”, or full sentences such as “Overall, the customer seems satisfied, but there’s a minor complaint.”

A recent incident report shows that when Model B is enabled, the dashboard’s weekly sentiment trend line becomes unstable because the same type of comment is sometimes mapped to different labels across runs, and some outputs fail parsing entirely. Example comment: “The update fixed my crash, but the new UI is confusing.” Example LLM outputs observed for that same comment: (1) “mixed feelings”, (2) “Overall positive with a caveat.”, (3) “Neutral.”

As the owner of the classification service, propose a concrete end-to-end decision policy that (a) uses prompt-completion classification with an explicit label-mapping step, (b) defines how to handle ambiguous or non-canonical generations so the service always returns exactly one of the three labels, and (c) explains when and how you would use Model A’s BERT probabilities as a fallback or tie-breaker to improve consistency without changing the label set. Your answer must specify the mapping rules/logic (not just “use heuristics”) and justify how the policy reduces instability while preserving the intent of polarity classification.

Designing a Consistent Polarity Classification Service Across BERT and Prompt-Completion Outputs

You are designing a single internal API endpoint, `POST /polarity`, that must return exactly one label from {POSITIVE, NEGATIVE, NEUTRAL} for each incoming customer message. For cost and latency reasons, the service will use two backends: (1) a fine-tuned BERT single-text classifier that outputs a probability distribution over {POSITIVE, NEGATIVE, NEUTRAL}, and (2) a prompt-completion LLM that returns free-form text (sometimes a single word like “positive”, sometimes a sentence like “Overall the tone is mixed but leans negative.”). Create a concise design spec for this endpoint that includes: (a) the prompt template you will use for the LLM to elicit a completion suitable for polarity classification, (b) a label-mapping strategy that deterministically converts the LLM’s completion into one of the three labels (including how you handle outputs that do not contain the exact label words), and (c) a decision policy for when to trust BERT vs the LLM (or how to combine them) that explicitly uses BERT’s probabilities and the mapped LLM label to produce the final label. Your answer must be specific enough that an engineer could implement it without additional clarification.

Learn Before

Related