Is there a limit on how many entity slots can be filled in one utterance? For example, could a user say "I want to book a trip for 2 passenger on an Acela train for business class on February 27th and it would capture <2 passengers>, <Acela>, <business class>, and <February 27>?
Sure, you would just create two custom entities: FromAccount and ToAccount. When the framework classifies entities, it does so in context, so it is aware of the rest of the sentence when it is trying to classify "Checking" and "Savings".
That said, this is also a good example of something to be cautious with because while the framework will probably have no problem at all with this specific problem, its accuracy might start to degrade quickly if you were also asking it to identify SecondaryAccount and TertiaryAccount and BackupAccount, etc.
@cchannon Thanks for this detailed answer! It makes sense that the more entity types that could match, the harder it will be for the model to determine which entity you are trying to fill.
Side question, do you see a way Copilot Studio could handle an utterance like "I want to transfer from a checking to a savings account" and be able to fill a "from account" and a "to account" if the entity is the same type for both (account type)?
There is no hard limit that I am aware of, and there is none documented in the service quotas and limits or the Entities documentation pages.
However, there is a practical limit on this kind of extraction. The model in question is putting out a reasonable prediction:
That second part is the tricky bit because the more entity types that it could match, the higher the likelihood that you'll 'confuse' the model and get inaccurate results. This is an inescapable statistical reality. So, if you keep adding a whole ton of custom entities what you'll eventually find is that the model accuracy degrades. There's no way to say when or how fast, but eventually you'll start to see the performance drop.
So, again, there is no hard cap I know of, but if you're thinking of trying to use this to extract hundreds of distinct custom entity types, this is not the right solution for you.
Share
Report
All responses (
Answers (
4,702