{"id":177,"date":"2017-07-18T02:01:32","date_gmt":"2017-07-18T02:01:32","guid":{"rendered":"http:\/\/freedville.com\/blog\/?p=177"},"modified":"2019-04-12T14:12:46","modified_gmt":"2019-04-12T14:12:46","slug":"balancing-precision-and-recall-in-your-cognitive-system","status":"publish","type":"post","link":"http:\/\/freedville.com\/blog\/2017\/07\/18\/balancing-precision-and-recall-in-your-cognitive-system\/","title":{"rendered":"Balancing precision and recall in your cognitive system"},"content":{"rendered":"

In building a cognitive model it can be difficult to know when it’s accurate enough<\/a>.  (You are measuring your daily performance, right?)  We know that cognitive performance often involves making a tradeoff between the competing factors of precision and recall.  In this post I’ll explore some strategies for dealing with the tradeoffs.<\/p>\n

Strategy 1: Use different F-scores<\/strong><\/p>\n

In most of my posts I describe using F1, but you can use any F-score<\/a>.  F1 gives equal weight to precision and recall.  Depending on your application certain kinds of mistakes are worse than others and a different F-score is appropriate.  You can plug other constants into the F-score formula to favor precision or recall.<\/p>\n

If you are building an application where not surfacing a potential correct answer is a big deal (for instance, a search application), you should favor recall by using F2.  This punishes false negatives twice as much as false positives.  If the worse thing your application can do is produce a false positive, favor precision by using F0.5.  If your users demand an even more extreme balance, ratchet up (or down) that F-score coefficient as needed.<\/p>\n

You get what you measure, so it is important to decide the metric that measures success.<\/p>\n

Strategy 2: Use multiple layers with different optimizations<\/strong><\/p>\n

This is an approach popularized by the Jeopardy!-playing Watson system<\/a>.  The first layer in that system favored recall, generating multiple hypotheses that were sent to a second layer that merged and ranked them.  This second layer favored precision, keeping only the highest ranked answer (and only if it cleared a confidence threshold).<\/p>\n

This approach is adaptable to other cognitive approaches.  Let’s assume we have a Product Color annotator that runs on product descriptions and has a 60% F1 score.<\/p>\n

Example resolution layer with majority voting<\/h2>\n\n\n\n\n\t\n\n\t\n\t\n\t
Product #<\/th>Annotation layer results<\/th>Voting layer result<\/th>Actual color<\/th>\n<\/tr>\n<\/thead>\n
Product 1<\/td>green, green, purple<\/td>green<\/td>green<\/td>\n<\/tr>\n
Product 2<\/td>red, red, blue, red<\/td>red<\/td>red<\/td>\n<\/tr>\n
Product 3<\/td>yellow, orange<\/td>-<\/td>yellow<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n

We can improve our detection of colors using a resolution layer, in this case simple majority voting.  Many other resolution techniques are possible.  The resolution layer allows the NLP layer to be a little looser, favoring recall, and tightening (favoring precision) can happen later.<\/p>\n

Strategy 3: Build a dynamic confidence model<\/strong><\/p>\n

Rather than using a one-size-fits-all method to balance precision and recall, you can adapt the balance between them on a case-by-case basis.  If you are using rules-based NLP, you could measure the precision of each of your rules and let the best rules ‘overrule’ the weakest.  You could examine document metadata and decide to trust (or be suspicious of) results from documents of given type or age.<\/p>\n

The model should be tuned from experience, or better yet actual results, to improve the chances of imperfect tools giving quality results.<\/p>\n

This strategy is a variation of Strategy 2 using a much fancier layer.  For additional ideas, see my previous post about building an NLP confidence model<\/a>.<\/p>\n

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

There are multiple strategies you can use to balance precision and recall in your cognitive system.  First decide what types of errors are most harmful to your system, then use these strategies to balance precision and recall for optimal results.<\/p>\n","protected":false},"excerpt":{"rendered":"

In building a cognitive model it can be difficult to know when it’s accurate enough.  (You are measuring your daily performance, right?)  We know that cognitive performance often involves making a tradeoff between the competing…<\/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,2,4,6],"_links":{"self":[{"href":"http:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/posts\/177"}],"collection":[{"href":"http:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/comments?post=177"}],"version-history":[{"count":4,"href":"http:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/posts\/177\/revisions"}],"predecessor-version":[{"id":417,"href":"http:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/posts\/177\/revisions\/417"}],"wp:attachment":[{"href":"http:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/media?parent=177"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/categories?post=177"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/freedville.com\/blog\/wp-json\/wp\/v2\/tags?post=177"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}