Dialogflow entity matching Issues
up vote
0
down vote
favorite
I’ve been trying the Dialogflow application for a few days and I’ve encounter some obstacles that I’m not sure how to perform.
Let’s say I have an intent which relate to banking situation. The intent has a slot filling which NLU has to detect a parameter in the user input sentences ( such parameter would be a bank accounts, phone number, birthday, etc.,) and this bot has to be multilingual. The issue occurs when the system provided entities are not the same in each supported language (i.e en-US has entities of sys.phone-number but this entity is not exist in Th language).
So my question is
- Am I suppose to create an entity which has every combination of account number format (as a synonym) to make the NLU be able to detect the account number in user sentences
- I understand that dialogflow has an API which support batch upload entities. Is this the right way to do it?
dialogflow
add a comment |
up vote
0
down vote
favorite
I’ve been trying the Dialogflow application for a few days and I’ve encounter some obstacles that I’m not sure how to perform.
Let’s say I have an intent which relate to banking situation. The intent has a slot filling which NLU has to detect a parameter in the user input sentences ( such parameter would be a bank accounts, phone number, birthday, etc.,) and this bot has to be multilingual. The issue occurs when the system provided entities are not the same in each supported language (i.e en-US has entities of sys.phone-number but this entity is not exist in Th language).
So my question is
- Am I suppose to create an entity which has every combination of account number format (as a synonym) to make the NLU be able to detect the account number in user sentences
- I understand that dialogflow has an API which support batch upload entities. Is this the right way to do it?
dialogflow
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I’ve been trying the Dialogflow application for a few days and I’ve encounter some obstacles that I’m not sure how to perform.
Let’s say I have an intent which relate to banking situation. The intent has a slot filling which NLU has to detect a parameter in the user input sentences ( such parameter would be a bank accounts, phone number, birthday, etc.,) and this bot has to be multilingual. The issue occurs when the system provided entities are not the same in each supported language (i.e en-US has entities of sys.phone-number but this entity is not exist in Th language).
So my question is
- Am I suppose to create an entity which has every combination of account number format (as a synonym) to make the NLU be able to detect the account number in user sentences
- I understand that dialogflow has an API which support batch upload entities. Is this the right way to do it?
dialogflow
I’ve been trying the Dialogflow application for a few days and I’ve encounter some obstacles that I’m not sure how to perform.
Let’s say I have an intent which relate to banking situation. The intent has a slot filling which NLU has to detect a parameter in the user input sentences ( such parameter would be a bank accounts, phone number, birthday, etc.,) and this bot has to be multilingual. The issue occurs when the system provided entities are not the same in each supported language (i.e en-US has entities of sys.phone-number but this entity is not exist in Th language).
So my question is
- Am I suppose to create an entity which has every combination of account number format (as a synonym) to make the NLU be able to detect the account number in user sentences
- I understand that dialogflow has an API which support batch upload entities. Is this the right way to do it?
dialogflow
dialogflow
asked Nov 22 at 5:36
Varut Jitthamwong
13
13
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53424473%2fdialogflow-entity-matching-issues%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown