I have a single slot intent with an AMAZON.DATE slot type and another single slot intent with AMAZON_FOUR_DIGIT_NUMBER slot type. When I give a date utterance such as "february twenth-fourth ninteen sixty-seven", the intent with the AMAZON_FOUR_DIGIT_NUMBER slot type is getting invoked instead.
If i add words before the AMAZON.DATE slot type like this: "my birthday is february twenth-fourth ninteen sixty-seven", it works properly.
I've tried many different dates and get the same result. Clearly, the name of the month in the utterance should never be confused with an intent that expects only digits so I have no idea how this could fail to go to the right intent, especially when the profiler itself captured and converted it properly as an "other considered intent".
Why is this happening and how to fix it?
Attached below is the utterance profiler result:
