| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Dialogflow
Entity for number of ingredients and number of recipe steps
...
Another way to improve your Dialogflow agent is to enable a user to include multiple requests in a single user expression. You can achieve this simply by including many more phrases such as “I’d like a Chinese recipe with less than 8 ingredients”. This will ensure that your conversational agent can recognize multiple filter requests.
Prolog and Patterns
Retrieving the (number of) ingredients and recipe steps
...
| Note |
|---|
It is very important to make sure that values are of the right type. The values that Dialogflow returns are often atoms or strings. Comparing strings to numbers using the < operator, for example, will result in a Type error in SWI Prolog that will terminate the MARBEL agent. To avoid such issues, we therefore always need to make sure that values that must be numbers (because they match with @sys.number entity type in Dialogflow) are converted to numbers again in Prolog. There are predicates defined for this purpose in the |
Now add a similar rule that applies a filter for the nrSteps feature; your Training phrases should dictate how to read the constraint. I.e., if your phrase says “less than N recipe steps” than you should write code that implements the filter to mean exactly that.
Add a similar rule that applies a filter for the servings feature. You probably want to make sure that a recipe has exactly the right number of servings that the user asked for.
Finally, add a rule that applies a filter for the duration feature. This feature is a bit more tricky and you should take the warning above about data types to heart. However, most of the work has already been done for you in the
dialog_update.mod2gfile in a step called Pre-process parameters of intent. In this step, the duration values received from Dialogflow are transformed to minutes (numbers) using theduration_to_minpredicate defined in theutils.plfile. This means that to define the rule for filtering, you simply need to look up the time it takes to cook a recipe in the database (specified in minutes), and compare that value with the maximum duration that the user specified.
Visuals
Extend the recipe confirmation page
...