Dialogflow

Extend your addFilter intent and add training phrases and entities for excluding an ingredient (type). For example, your Dialogflow agent should be able to make sense of the phrase “recipe without cucumber”. To make sure that the MARBEL agent will be able to handle these ingredients differently from the ones a user wants to include, you should create new parameter names that suggest the ingredient (type) should be excluded instead of included. The table in the Action and parameters section should be extended as follows:

...

Make sure to annotate plenty of phrases again with these examples of the use of these parameters! Only if there are enough of these phrases will your Dialogflow agent be robust for all kinds of user input.

As a next step, in a similar vein, extend your agent such that it is able to exclude a cuisine or a dietary restriction (a recipe should not be Japanese or vegan). The table in the Action and parameters section for your addFilter intent should be extended as follows:

...

Prolog and Patterns

In your recipe_selection.pl file, add the following rules for applying the corresponding filters to the new entities we introduced above. You should define four applyFilter/4 rules for the following clauses:

...

applyFilter('excludeingredient', Ingredient, RecipeIDsIn, RecipeIDsOut): There is a predicate in the ingredient_hierarchies.pl file which might be useful.

...

where the first argument is instantiated with, respectively, ‘excludeingredient', 'excludeingredienttype',

...

applyFilter('excludedietaryrestriction', Restriction, RecipeIDsIn, RecipeIDsOut)

...

'excludedietaryrestriction', and 'excludecuisine'. You should note that to implement these rules it is sufficient to simply require the opposite (the negation) of the basic condition that you used for the rule for 'ingredient', etc.

Visuals

Nothing we ask you to do here for this capability. It’s up to you.

...