Slot filling

On this page 7

Slot filling is the task of identifying and extracting the specific parameter values that a conversational system needs to carry out a request, such as a destination, a date or a quantity, and assigning each value to a predefined slot in a task schema. In speech & language AI, it is a core component of spoken language understanding, where it usually runs together with intent recognition: the intent says what the user wants to do, and the slots say with which details.

A request such as “book a table for four at seven tomorrow” carries the intent restaurant booking and three slot values: party size, time and date. Without reliable slot filling, a voice assistant or chatbot can recognize the goal yet still fail to act, because it lacks the arguments the backend action requires.

How slot filling extracts values from an utterance

Slot filling works by labeling the tokens of an utterance with slot names and then normalizing the labeled spans into values the application can use. The classical formulation treats it as sequence labeling with the BIO scheme, in which each token is tagged as the beginning of a slot, inside a slot or outside any slot.

The process normally passes through several stages. The system first receives text, either typed or produced by speech-to-text, then tags candidate spans, resolves them against the slot ontology, and finally converts surface forms such as “tomorrow” or “seven” into canonical values like an ISO 8601 date and a 24-hour time.

The following table shows how one utterance is tagged and normalized in a typical travel booking schema.

Token spanBIO tagSlotNormalized value
from BostonB/I-originoriginBOS
to DenverB/I-destinationdestinationDEN
next FridayB/I-datedeparture_date2026-11-27
two adultsB/I-passengerspassenger_count2
I need a flightOnonenot applicable
BIO tagging and normalization for a flight request

Tagging and normalization are distinct problems. A model can find the span “next Friday” correctly and still produce a wrong value if the date resolver ignores the user’s time zone, which is a frequent source of silent errors in production.

Approaches and model architectures

Slot filling methods have moved from hand-written grammars to statistical taggers and then to pretrained transformer encoders and generative language models. Each generation trades control for coverage, and many deployed systems still combine several approaches in one pipeline.

ApproachTypical techniqueStrengthWeakness
Rule-based grammarsRegular expressions, context-free grammarsPredictable, no training dataBrittle with paraphrases
Statistical taggersConditional random fieldsRobust with modest dataNeeds feature engineering
Neural sequence labelersBiLSTM-CRF, BERT token classificationHigh accuracy on fixed schemasNeeds labeled spans per domain
Joint intent and slot modelsShared encoder with two output headsIntent and slots inform each otherCoupled retraining for any change
Generative extractionLLM prompted to emit JSON slotsZero-shot schemas, flexible wordingHallucinated or unnormalized values
Main slot filling approaches and their trade-offs

Joint models are popular because intent and slots are mutually informative: knowing that the intent is a weather query makes “Paris” far more likely to be a location than a person. With large language models, slot filling increasingly resembles function calling, where the model fills the arguments of a typed tool signature, but the underlying task and its evaluation remain the same.

Slot filling within dialogue and information extraction

Slot filling sits between intent recognition and dialogue management, and it is easy to confuse with neighboring tasks that also extract spans. The distinction lies in what defines the labels: slot filling uses a task-specific schema, whereas named entity recognition uses general entity types.

TaskOutputLabel sourceTypical use
Slot fillingValues for schema slotsApplication task schemaExecuting user requests
Named entity recognitionTyped entity spansGeneral types such as person or locationIndexing and analytics
Intent recognitionOne goal label per utteranceSet of supported actionsRouting the request
Relation extractionEntity pairs with a relationRelation inventoryBuilding knowledge graphs
Dialogue state trackingSlot values across turnsTask schema plus historyMulti-turn conversations
Slot filling compared with related language tasks

In multi-turn dialogue, slot filling feeds dialogue state tracking, which accumulates values across turns and handles corrections such as “actually, make it Saturday”. The dialogue manager then checks which required slots are still empty and asks targeted follow-up questions, a strategy known as slot elicitation. The phrase also has a second, older use in knowledge base population, where systems fill attributes of an entity from documents, but conversational systems are the dominant context.

Designing slots and measuring quality

Good slot filling starts with a well-designed schema: clear slot names, explicit value types, a defined list of required versus optional slots, and documented normalization rules. Ambiguous schemas, for example separate “start_time” and “time” slots with overlapping meaning, produce inconsistent annotations and lower accuracy no matter which model is used.

Quality is measured at more than one level, because a high token score can hide failures that matter to users.

MetricWhat it measuresTypical reading
Slot F1Exact span and label match, micro-averagedOften above 0.95 on clean benchmarks
Value accuracyCorrectness after normalizationLower than span F1 for dates and times
Sentence-level accuracyIntent and all slots correct togetherThe best proxy for task success
Joint goal accuracyFull dialogue state correct per turnUsed for multi-turn systems
Common evaluation metrics for slot filling

Scores on standard benchmarks such as ATIS and SNIPS are close to saturation, so they say little about real-world robustness. Evaluations on in-domain user logs, spoken input with recognition errors and rare slot values give a far more honest picture of production performance.

Limitations and common failure modes

Slot filling fails most often at the boundaries of what the schema and training data anticipate. In voice systems, speech recognition errors propagate directly into slot values, so a misheard digit in a phone number or an account code cannot be repaired by the tagger alone.

SymptomLikely causeRemedy
Wrong date or time valueMissing time zone or relative date logicResolve against user locale and session time
Value assigned to wrong slotOrigin and destination confusionAdd contrastive training examples
Unknown city or product missedOut-of-vocabulary valuesUse catalog lookup and fuzzy matching
Invented valuesGenerative model hallucinationConstrain output and validate against catalogs
Corrupted numbers from speechRecognition errors on digitsConfirm critical slots with the user
Typical slot filling errors, causes and remedies
  • Overlapping and nested values, such as a hotel name that contains a city name, break simple BIO tagging.
  • Implicit values inferred from context, for example “the usual” or “same as last time”, require dialogue history rather than span extraction.
  • Code-switching and low-resource languages reduce accuracy sharply when labeled data exist only in one language.
  • Explicit confirmation of high-risk slots, such as payment amounts, remains necessary even with accurate models.

In plain words

Slot filling is how a voice assistant or chatbot picks out the details it needs from what you say. Think of a paper form with blank boxes for date, time and number of people. When you say “a table for four at seven tomorrow”, the system reads your sentence and writes each detail into the right box.

If a box stays empty, a well-built assistant simply asks you for it. The key point is that understanding what you want is not enough; the system also has to capture the exact details before it can actually do anything for you.

A real-world example

A regional bank runs a phone assistant for card services. A caller says, “I want to raise my daily limit to fifteen hundred on my debit card.” The speech recognizer produces text, the intent model selects change card limit, and the slot filler extracts three values: card type as debit, limit type as daily and amount as 1,500 in the account currency.

During the first month, logs showed that amounts spoken as “fifteen hundred” were sometimes normalized to 15 or 100 because the number parser expected digit-by-digit speech. The team added a dedicated number normalizer, contrastive examples for daily versus monthly limits, and a spoken confirmation step for the amount slot.

After these changes, sentence-level accuracy rose on the card-limit intent, and the share of calls transferred to human agents for this request dropped noticeably. The confirmation step also prevented incorrect limit changes from reaching the core banking system, which was the outcome that mattered most to the operations team.