I’m attempting to train a bot that uses Duckling to identify numbers and times. I had previously created the following entity slots:
- number - timeAbs - timeAgo - yearBorn - zipCode - time
Duckling seems to find entities of its own that are called similar things. When I train interactively with Duckling and append the resulting data from the session, Duckling is creating synonyms and nlu.md data that are tagged to specific times and numbers:
[6:45](time:2019-04-23T18:45:00.000-07:00)[6:45](timeAbs) [around noon](time:2019-05-02T12:00:00.000-07:00)[noon](timeAbs)
Do you recommend that we rely only upon Duckling for training? It seems that Rasa NLU entities are decoupled completely from Duckling entities, and that Duckling does not feed features to Rasa NLU entity prediction. However, if we use Duckling entities only for training, we end up with these ultra-specific times assigned to the entities.
Finally, I want to confirm that all discovered Duckling entities must also be listed under “domain.yml”'s entities listing (i.e. time, number), or is this unnecessary?