I have a form which includes a request to enter a currency (e.g., BTC) or currency pair (e.g., lrcbtc). There are thousands of these and they change, so a lookup table isn’t so great. In some cases, the “currency” intent is being recognized, but the “currency” entity isn’t being picked up so my form workflow breaks.
What is the best approach to force or give a hint so the entity is actually picked up? I thought I could do in slot_mappings but I can’t see how I can get access to the original text (if so, I could do a sanity check on text for the currency slot and then assign that). Was also thinking of a custom NLU component where I rewrite “lrcbtc” into “symbol lrcbtc” and then train on this pattern. However, I can’t see how I can see the current slot-setting context necessary to know when I should rewrite text.
Is there a sane way to solve this problem?