Which LUIS Custom Entity Minimizes Training Utterances for Airport Names?
You are building an Azure AI Language Understanding solution. You discover that many intents have similar utterances containing airport names or airport codes. You need to minimize the number of utterances used to train the model. Which type of custom entity should you use?
Community Votes
61% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests the difference between LUIS entity types for synonym mapping: list entities provide exact and synonym matches that eliminate repetitive training utterances, while pattern.any is for variable-length pattern extraction.
In Azure AI Language Understanding, list entities handle fixed sets like airport names and codes via synonyms, reducing the number of training utterances needed. This page explains why the list entity (D) is the correct choice for minimizing utterances with synonymous airport identifiers.
Many candidates choose pattern.any (A) because it handles variable-length entities in patterns, but pattern.any still requires patterns and utterances and does not natively map synonyms like airport codes to full names.
Community Discussion (16 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
A LUIS list entity is designed for a fixed, closed set of related words and their synonyms. By defining an Airports list with items such as John F. Kennedy International Airport and synonyms like JFK, you can cover many variations without adding a separate training utterance for each form. Microsoft's own documentation uses an airport example for list entities, showing that a single item can include city names, airport codes, postal codes, and phone area codes as synonyms. This synonym mapping directly minimizes the number of utterances needed to train the model, making D the correct choice.Why the Other Options Are Wrong
Pattern.any (A) is used inside patterns to extract variable-length entities, but it does not provide synonym mapping and still relies on pattern utterances to work. A machine-learning entity (B) learns from labeled utterances, so it typically requires more examples to generalize, opposite of the goal. A regular expression entity (C) extracts text that matches a regex, which is useful for structured formats but not for associating synonymous airport names and codes. None of these reduce utterance count as directly or as reliably as a list entity.Community Comment Notes
The community favors D, though a notable minority chose A. Moneybing and Andriki support list entities, with Andriki noting they are a "fixed, close set of related words." pmd30 quotes Microsoft's list entity example that includes "airport (Sea-tac), airport code (SEA), postal zip code (98101)" as synonyms, which mirrors the airport scenario. Toby86 and syupwsh argue for pattern.any because it handles multiple forms, but pabsinaz summarizes the trade-off well: "Either A or D, both works. A less development effort, D a better solution." Since the question asks to minimize utterances, the list entity is the better fit.Official Reference
Exam Strategy
For AI-102 LUIS entity questions, memorize the core purpose of each type: list = fixed set with synonyms and minimal utterances; pattern.any = variable-length extraction inside patterns; regex = structured formats; machine-learning = trained from labeled examples. If the scenario mentions known synonyms like airport codes, choose list.
Frequently Asked Questions
Why is a pattern.any entity not the best choice for airport names and codes?
Pattern.any extracts variable-length entities inside patterns, but it does not map synonyms like JFK to John F. Kennedy International Airport; list entities do that without extra utterances.
Does a list entity reduce training utterances in LUIS?
Yes, because each list item can have many synonyms, so one labeled example can cover numerous variations without adding separate utterances.