A parks chatbot hears “Is the big park open Sunday?” when the city has several similarly named parks. What conversational design should run before retrieval?
Select an answer to reveal the explanation.
Short Explanation
When you hear “the big park,” ask the resident which park they mean before you look up its hours or policies. Clarification first keeps you from guessing across similar names and giving the wrong answer.
Full Explanation
When a resident asks whether “the big park” is open Sunday, the name may refer to several similarly named parks. The chatbot should ask which park the resident means, then retrieve information using the confirmed park identifier. Resolving the ambiguity first keeps the query precise and helps prevent an answer about the wrong facility. Retrieving every park policy and asking the FM to guess wastes context, increases the chance of conflicting information, and leaves the intended park unresolved. Always replying with aquatics center hours ignores the resident’s question and provides unrelated information. Sending the request directly to FAQ search and using the first matching park name skips clarification; a first match may be the wrong park, so its hours or policies could mislead the resident. Exam caveat: when a question highlights ambiguous civic entity names, clarify before retrieval rather than returning all candidates or trusting the first match. Practical check: maintain a park identity catalog with aliases, trigger a clarification turn when entity-resolution confidence is low, pass only the confirmed park ID into retrieval filters, and track wrong-facility answer rates after releases.