如何处理太大的实体 [英] How to handle entities that are too large
问题描述
您好，
我们有一个生产机器人运行，我们的{PersonName}实体即将过大。我们的规范形式是用户的全名（我们有大约6500个用户），同义词是first，last，tinyutives（miki，mike for michael），首选名称（Jiao
是George）。
We have a production bot running where our {PersonName} entity is about to be too large. Our canonical form is a user's full name (we have about 6500 users) and the synonyms are first, last, diminutives (miki, mike for michael), and preferred name (Jiao is George).
我正在探索的一个可能的解决方案是将实体分解为两个（PersonFirstName，PersonLastName）并且具有复合实体PersonName，这将极大地减少名称组合。但是，我们目前有多个依赖于{PersonName}的其他复合实体
，我找不到使用嵌套复合实体重新创建这些实体的方法。
One potential solution I am exploring is to break the entity into two (PersonFirstName, PersonLastName) and have a composite entity PersonName which would drastically reduce the combinations of names. However, we currently have multiple other composite entities that depend on {PersonName} and I can not find a way of recreating these using nesting composite entities.
什么是处理增长幅度大于20,000实体限额的实体的首选方法？
What is the preferred method for dealing with an entity that is growing larger than the 20,000 entity limit?
谢谢，
stikemanley
stikemanley
推荐答案
你好，
你可以使用预先构建的
PersonName 实体它标识了没有经过任何培训的人的完整名称。
You can use the prebuilt PersonName entity which identifies the complete name of the person without any training.
如果你还想要
extract 你可以使用像MyName这样的简单实体的名字和姓氏，并像MyFirstName一样添加角色和MyLastName。
If you would still like to extract the first and last names you can use a simple entity like MyName and add roles to it like MyFirstName and MyLastName.
然后在意图中添加话语并相应地标记它们。
Then add utterances to the intent and label them accordingly.
标签前：
标签后：
在此之后训练你的应用并发布它。它现在应该在JSON响应中显示这些标签，可以在您的应用程序代码中使用。
Train your app after this and publish it. It should now show these labels in the JSON response which can be used in your application code.
由于您没有使用预建的PersonName实体，您可能需要使用您拥有的足够名称来训练应用程序，然后将其发布。我希望这可以帮助您避免使用复合实体。
Since you are not using prebuilt PersonName entity you might need to train the app with enough names you have and then publish it. I hope this helps you to avoid using composite entities.
这篇关于如何处理太大的实体的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
