{"id":34,"date":"2016-11-12T01:35:13","date_gmt":"2016-11-12T01:35:13","guid":{"rendered":"http:\/\/freedville.com\/blog\/?p=34"},"modified":"2019-04-12T14:14:10","modified_gmt":"2019-04-12T14:14:10","slug":"training-a-personal-chatbot-with-watson-developer-cloud-apis-part-2","status":"publish","type":"post","link":"https:\/\/freedville.com\/blog\/2016\/11\/12\/training-a-personal-chatbot-with-watson-developer-cloud-apis-part-2\/","title":{"rendered":"Training a personal chatbot with Watson Developer Cloud APIs – Part 2"},"content":{"rendered":"

In part 1 of Training a personal chatbot with Watson Developer Cloud APIs<\/a> I gave an intro to text classification and how you could use it to create a chat bot that screened your incoming questions on the basis of whether or not they were related to lunch.<\/p>\n

Covering more topics with classification<\/strong><\/p>\n

My first classification scheme was relatively simple – “lunch or not lunch?”  This was a very coarse classification scheme but still presented challenges in gathering useful training data.  The end result is not quite useful enough for a chat bot – I can hardly give an interesting response to a question knowing only that it pertains to lunch.  The two most important parts about lunch are “when” and “where”.  Let’s consider the possibilities.<\/p>\n

Given a question about lunch, it could be a “when should we go” question, “where should we go” question, “when and<\/em> where should we go” question, or an “other” lunch question.  Thus, I could reasonably sub-divide my “lunch” classification into four sub-classifications.<\/p>\n

Alternatively, I could think about classifying in orthogonal dimensions.  My first dimension could be “lunch vs other”, the second dimension could be “when vs not_when”, the third dimension could be “where vs not_where”.  (Or, my second dimension could be “when vs where vs neither”).  Then, I could classify a piece of text against both dimensions simultaneously and take the intersection.  If the first classifier says it’s a “lunch” question, the second says it’s a “when” question, then the intersection means it’s a “when should we lunch” question.<\/p>\n

General or specific classifiers – which are better?<\/strong><\/p>\n

Should you prefer very specific classifiers on a single dimension, or more general classifiers on multiple dimensions?  A classic “it depends” question!  You should be able to get good results with either approach, if you have sufficient training data.  (This is a big if, we’ll come back to it.)  Specific classifiers should in theory be extra precise, if trained well.  There is a significant benefit to the ‘general’ classifiers method however.  Consider how many topics you want your chat bot to handle.  Let’s say you will want your chat bot to not just handle lunch arrangements but also regular business meetings.  Business meetings will also include where and when aspects.  If you use ‘general’ classifiers, you have the opportunity to reuse existing classifiers and will have less training to do overall.<\/p>\n

What does the data allow?<\/strong><\/p>\n

The philosophical questions sometimes have to take a backseat to what the data allows.  Recall that my initial possible training data set is 66,000 questions pulled from my chat transcripts.  Let’s see what the data allows in terms of lunch-related questions.  For a shortcut, I will run a grep for the term lunch and the seven restaurants my team visits the most:<\/p>\n

egrep -i \u201clunch|carmen|moe|lime|greek|brixx|randys|kabob\" SametimeQuestions.txt<\/code><\/p>\n

This yields approximately 100 questions.  Through a quick scan, only 9 appear to be “when” questions.  A similar number are “where” questions.  (The vast majority are simply “interested in lunch?” questions or not even related to a lunch invitation).  9 examples is not going to be enough for classifying, I don’t want to think about using a classifier that doesn’t have at least 20 examples, and I don’t want to generate synthetic examples since I know they won’t be representative of questions I will actually receive.  Thus the data appears to be forcing our hand.<\/p>\n

It is worth verifying, do we have enough when and where questions to classify? I again use a simple grep as a proxy for estimating possible training data. Most invitations, lunch or otherwise, happen on 15-minute intervals, so checking the “minutes” value of the clock plus the “when” keyword is a good proxy for how many “when” questions I will have. For “where” questions, I use the obvious keyword plus a handful of common locations.<\/p>\n

egrep -i \"00|15|30|45|when\" SametimeQuestions.txt
\negrep -i \"where|carmen|moe|lime|greek|brixx|randys|kabob\" SametimeQuestions.txt | wc -l<\/code><\/p>\n

These queries yield approximately 800 and 500 questions, respectively. Thus, I should have plenty of training data available to build multiple, generalized classifiers.<\/p>\n

Training data for two dimensions<\/strong><\/p>\n

At a high level, the training exercise looks a lot like what we did in the previous post, we just have more work to do since we are doing more dimensions.  Just grab questions and manually classify them.  To train against “when”\/”not when”, I added 70 questions from my “00|15|30|45|when” question set, being sure to include questions that used times or the word “when” in a way that did NOT indicate a when question.<\/p>\n

I added these questions to the same spreadsheet as my first training data, simply adding a column to represent when\/not-when.  Thus my columns are question, lunch\/other, when\/not-when.  Note that this requires additional classification, adding when\/not-when to my original lunch\/other questions, and adding lunch\/other to the new when\/not-when questions.  However this is largely an Excel “fill” exercise – most of the original questions were not-when, and most of the new questions are other (not-lunch).<\/p>\n

Here’s a sample of the new training data (full data here: Lunch vs Other and When vs Not-When NLC Training Data<\/a>):
\nlunch @ 1130?,lunch,when
\nare you going out for lunch today?,lunch,not_when
\nAndrew- u have extra shinguard?,other,not_when
\nlet's chat after I grab some lunch .. you have some time this afternoon?,other,when
\ndo we have a room for the 1:30?,other,not_when
\ndoes this happen when you build and deploy?,other,not_when
\nwhen is your next meeting?,other,when<\/code>
\nThere are a few possibilities for how to proceed, depending on whether we want to use multiple Natural Language Classifier instances (one per dimension) or whether we want to “hack” Natural Language Classifier by forcing it to run multi-dimensional classification in a single instance.<\/p>\n

Using two classifiers<\/strong><\/p>\n

The first method is to use two classifiers.  I can take my 2d training file and alternately delete the “lunch” or “when” column, to create two training files, each of one dimension.  See When vs Not-When NLC Training Data<\/a>.<\/p>\n

After training my “when” classifier, I ask it the same questions I asked in my previous post<\/a>.  The “lunch @ 1145” question classifies as 86.5% confident to “when”.  Thus my two classifiers tell me with very high confidence that this is a “when lunch” question.  “sure, when do you need it by?” is 99.5% confidence for “when” and 99.4% “other”, clearly a “when not-lunch” question.  “does it work when you restart the build?” is 84.5% confidence for “not-when”.<\/p>\n

From these results you can see that the “when\/not-when” classifier performs very well, even better than the lunch\/other classifier described in my previous post.  This is not surprising when you consider it received twice as much training data.<\/p>\n

Thus, by using two classifiers and combining their results, you can get high confidence on each dimension and make a very good guess at a question’s true two-dimensional classification.<\/p>\n

Multiple dimensions in one classifier<\/strong><\/p>\n

I can upload my two-dimensional training data directly into a single classifier.  When I run a question against it, I get interesting results:<\/p>\n

curl -G -u \"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx\":\"xxxxxxxxxxxx\" https:\/\/gateway.watsonplatform.net\/natural-language-classifier\/api\/v1\/classifiers\/xxxxxxxxxx-nlc-xxxx\/classify --data-urlencode \"text=lunch @ 1145?\"
\n{
\n\"classifier_id\" : \"xxxxxxxxxx-nlc-xxxx\",
\n\"url\" : \"https:\/\/gateway.watsonplatform.net\/natural-language-classifier\/api\/v1\/classifiers\/8aff06x106-nlc-13700\",
\n\"text\" : \"lunch @ 1145?\",
\n\"top_class\" : \"lunch\",
\n\"classes\" : [ {
\n\"class_name\" : \"lunch\",
\n\"confidence\" : 0.8798495105446424
\n}, {
\n\"class_name\" : \"when\",
\n\"confidence\" : 0.06570656619039483
\n}, {
\n\"class_name\" : \"not_when\",
\n\"confidence\" : 0.04098451924057577
\n}, {
\n\"class_name\" : \"other\",
\n\"confidence\" : 0.013459404024386896
\n}<\/code> ]
\n}<\/code><\/p>\n

We can view this question as a “lunch” and “when” question because they are the highest confidence classifications.  But we lose significant fidelity against one of our dimensions, since the classifier tries to pick a primary classification.<\/p>\n\n\n\n\n\t\n\n\t\n\t\n\t\n\t\n\t\n\t\n\t
Question<\/th>Lunch confidence<\/th>Other confidence<\/th>When confidence<\/th>Not-when confidence<\/th>\n<\/tr>\n<\/thead>\n
sure, when do you need it by?<\/td>96.5%<\/td>0.3%<\/td>2.78%<\/td>0.5%<\/td>\n<\/tr>\n
talk after lunch?<\/td>64.0%<\/td>10.6%<\/td>22.0%<\/td>3.5%<\/td>\n<\/tr>\n
o'charleys?<\/td>7.5%<\/td>2.8%<\/td>88.2%<\/td>1.5%<\/td>\n<\/tr>\n
production?<\/td>4.2%<\/td>4.1%<\/td>1.3%<\/td>90.2%<\/td>\n<\/tr>\n
are we going to lunch today?<\/td>90.4%<\/td>0.8%<\/td>0.7%<\/td>8.1%<\/td>\n<\/tr>\n
does it work when you restart the build?<\/td>0.2%<\/td>97.8%<\/td>0.8%<\/td>1.1%<\/td>\n<\/tr>\n
what time is lunch?<\/td>3.4%<\/td>6.1%<\/td>88.7%<\/td>1.7%<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n

We can see this in the “O’Charley’s” (a restaurant we visit) and “production” questions.  The highest lunch\/other classification for both is “lunch”.  But how confident can we feel in the result?  The problem is that all classifier confidences must add up to 100%, and the highest-matching classification takes up too much of the confidence pie to make a great delineation on the second dimension.  If we had tried to force three dimensions of classification into this classifier, the additional dimensions would be even harder to tease out of the classifier.<\/p>\n

How many classifiers is best?<\/strong><\/p>\n

Simple classifiers can be called in parallel and their results can be combined in an intuitive way.  One classifier can be overloaded and produce multiple dimensions.  Overloading one classifier may simplify classifier management, and it surely cuts down on our API usage bill, but it makes it harder to get a true read of the confidence on all of the classification dimensions.  Your mileage may vary, but I prefer the higher fidelity of using multiple classifiers.<\/p>\n

Conclusion<\/strong><\/p>\n

You can classify text against multiple dimensions, assuming those dimensions are orthogonal.  This can be accomplished using specific multi-dimensional classifications (ex: when_lunch) or multiple, general classifications (ex: when, lunch).  Multiple, general classifications can be achieved with a single or multiple classifiers.  Experimentation will help you decide what classification techniques your data requires.<\/p>\n","protected":false},"excerpt":{"rendered":"

In part 1 of Training a personal chatbot with Watson Developer Cloud APIs I gave an intro to text classification and how you could use it to create a chat bot that screened your incoming questions…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[9,5,4],"_links":{"self":[{"href":"https:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/posts\/34"}],"collection":[{"href":"https:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/comments?post=34"}],"version-history":[{"count":8,"href":"https:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/posts\/34\/revisions"}],"predecessor-version":[{"id":426,"href":"https:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/posts\/34\/revisions\/426"}],"wp:attachment":[{"href":"https:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/media?parent=34"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/categories?post=34"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/tags?post=34"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}