Bummer! This is just a preview. You need to be signed in with a Basic account to view the entire video.
Intents, Entities, and Dialogs3:30 with Ben Jakuben
We are now going to zero in on the important things you need to know to build a chatbot using the Conversation Service: Intents, Entities, and Dialogs. Let's take a look at what they are and how they fit together.
- Watson Developer Cloud on GitHub
- Watson Starter Kits - These contain starter app code for common use cases.
- Intent: An intent represents the purpose of a user's input. You define an intent for each type of user request you want your application to support.
- Entity: An entity represents a term or object that is relevant to your intents and that provides a specific context for an intent. You list the possible values for each entity and synonyms that users might enter.
- Dialog: A dialog is a branching conversation flow that defines responses to the defined intents and entities. You use the dialog builder in the tool to create conversations with users to provide responses.
For more information, check out Configuring a Conversation workspace in the docs.
[MUSIC] Welcome back we're now going to zero in on
the important things that you need to know to build a chat bot using
the conversation service that we created earlier.
>> The first thing we should do is get a bird's eye view of what we're building and
what the overall ecosystem Looks like.
We have provided you with a sample web app that will be the client in this.
The web app is using some Watson SDKs to make it very easy to communicate with
the Watson APIs available along the Watson Developer Cloud over here.
Users will input text into our simplified app, but
not that Watson can process text, voice, and visual input.
Our app will first pass the input data To a new conversation service that we create.
Each time we use a service from Watson, we create our own instance to connect to.
That allows us to train our unique instance with our own custom data.
The conversation service processes the input using its underlying
natural language processing technology.
Later we'll see how to communicate with more than just one service.
As we go along and build this part,
it will help to think about how it fits into this overall picture.
Then, now seems like a good time to point out that IBM has a variety of And
s available to make it easy for you to get started on a new p[roject.
No matter what you are working on, the are available
on and helpful are available on this page.
Both of these links are available for you in the teahers notes.
Back in our diagram, let's zoom into the conversation service.
Like a regular conversation, a conversation service with Watson has
some key elements in the speech or text that are needed for understanding.
The Watson conversation service defined these parts as intents,
entities, and dialog.
And they work together to deliver a conversational response to the user.
An intent represents the purpose of a user's input.
You define an intent for each type of user request you want your application to
support In the tool the name of an intent is always prefixed the pound character.
To train the workspace to recognize your intents you supply lots
of examples of user input and indicate which intents they left.
>> An entity represents a term or object that is relevant to your intents And
that provides a specific context for an intent.
For example, an entity might represent a city where the user wants to find
a business location or the amount of the bill payment.
In the tool the name of an entity is always prefix with the @ character.
To train the workspace to recognize your entities you list the possible values for
each entity and synonyms that users might enter.
>> A dialog is a brancing converstaion flow that defines
responses to the defined intents and entities.
You use the dialog building inthe tool to create
conversations with users to provide responses.
You need to sign up for Treehouse in order to download course files.Sign up