Firstly - great tool thank you.
The WA classifier now supports using entities within intent training. For instance "Can I get a @PhoneModelName? "
https://console.bluemix.net/docs/services/conversation/intents.html#defining-intents
This is very useful when reusing bot training across multiple bots for instance "Hello @me" where the intent training can be ported across and @me @otherpeople be controlled as entities.
At the moment when creating test data, the WA-Testing-Tool, submits "Hello @me" without replacing the @me with a literal from the entity training. This means that these values almost always fail, even though they would pass if @me replaced with one of the literal values.
Ask is to download the entity training with the intent training. When the intent training trains the workspace, @entity should be passed as currently. But when the test set is created, the @entity should be replaced with a random synonym/literal from the entity training set.
Firstly - great tool thank you.
The WA classifier now supports using entities within intent training. For instance "Can I get a @PhoneModelName? "
https://console.bluemix.net/docs/services/conversation/intents.html#defining-intents
This is very useful when reusing bot training across multiple bots for instance "Hello @me" where the intent training can be ported across and @me @otherpeople be controlled as entities.
At the moment when creating test data, the WA-Testing-Tool, submits "Hello @me" without replacing the @me with a literal from the entity training. This means that these values almost always fail, even though they would pass if @me replaced with one of the literal values.
Ask is to download the entity training with the intent training. When the intent training trains the workspace, @entity should be passed as currently. But when the test set is created, the @entity should be replaced with a random synonym/literal from the entity training set.