{"id":4331,"date":"2017-08-04T19:06:27","date_gmt":"2017-08-04T10:06:27","guid":{"rendered":"http:\/\/blog.themusio.com\/?p=4331"},"modified":"2024-05-01T10:46:07","modified_gmt":"2024-05-01T01:46:07","slug":"coreference-resolution","status":"publish","type":"post","link":"https:\/\/blog.themusio.com\/?p=4331","title":{"rendered":"Coreference Resolution"},"content":{"rendered":"<h1>Table of Contents<\/h1>\n<ol>\n<li><a href=\"#orgf7da288\">Coreference Resolution<\/a>\n<ol>\n<li><a href=\"#org1fecf99\">goal<\/a><\/li>\n<li><a href=\"#org33744e7\">motivation<\/a><\/li>\n<li><a href=\"#org313e9ec\">ingredients<\/a><\/li>\n<li><a href=\"#org623154b\">steps<\/a><\/li>\n<li><a href=\"#orgbe92439\">outlook<\/a><\/li>\n<li><a href=\"#org31c2240\">resources<\/a><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<p><a id=\"orgf7da288\"><\/a><\/p>\n<h1>Coreference Resolution<\/h1>\n<p><a id=\"org1fecf99\"><\/a><\/p>\n<h2>goal<\/h2>\n<p>In this weeks blogpost we are going to shed light on coreference resolution in an end-to-end way as recently presented in the paper &#8220;End-to-end Neural Coreference Resolution&#8221;.<\/p>\n<p><a id=\"org33744e7\"><\/a><\/p>\n<h2>motivation<\/h2>\n<p>Solving tasks in an end-to-end fashion becomes more and more popular for several reason.<br \/>\nTrying to optimize several components or modules of a system simultaneously can be very difficult due to their complex intertwining.<br \/>\nBesides that multi-component system usually need a lot of hand-tuned parameters such as thresholds in order to decide which data to pass to the next stage.<br \/>\nThis is also the case for previous work on coreference resolution which relies on parse trees and hand-engineered algorithms for aligning mentions on top of these.<br \/>\nSystems designed in this way clearly do not easily generalize to other domains.<\/p>\n<p><a id=\"org313e9ec\"><\/a><\/p>\n<h2>ingredients<\/h2>\n<p>scoring, bidirectional lstm, pruning, convolutional layer, word embeddings, character embeddings, metadata embedding<\/p>\n<p><a id=\"org623154b\"><\/a><\/p>\n<h2>steps<\/h2>\n<p>The task of coreferencing can be summarized as detecting all expressions in some text which correspond to the same entity.<br \/>\nCoreference resolution is a rudimentary task needed for tackling context understanding, question answering, information extraction and hence dialogue generation.<br \/>\nIn more detail coreferencing refers to assigning an antecedent to every mention in an utterance, sentence or document.<br \/>\nNow relying on spans of several words for detecting these mentions allows one to move a way from generating a parse tree.<br \/>\nAnd an antecedent can be every span occurring previous to the actual mention.<\/p>\n<p>The model architecture in the above mentioned paper consists of a unary and pairwise scoring of spans.<br \/>\nThe unary scoring takes a span representation as input and tells us how likely it is that it is a mention.<br \/>\nThe pairwise scoring consumes two span representations and additional metadata such as the speaker(s), the genre and the distance between those spans.<br \/>\nSimple feed forward networks provide the parameters to learn a good scoring.<br \/>\nAt this point we have to explain the structure of the span representations.<br \/>\nFor properly detecting mentions not only the internal structure is of importance but also the context.<br \/>\nHence the authors rely a bidirectional LSTM with a standard attention mechanism as of now being the standard for processing sequential data.<br \/>\nPretrained word embeddings in form of 300-dimensional GloVe vectors as well as 50-dimensional vectors insensitive to word-ordering are fed to the LSTM.<br \/>\nTo resolve the internal structure one-dimensional convolutional filters of size 3,4 and 5 are used, which provide further 8-dimensional embeddings.<br \/>\nA span representation is then the concatenation of the result of the hidden states of the start and end position of the span, the attention state, as well as the size of the span.<\/p>\n<p>Obviously, splitting utterances into all possible spans and scoring all of these pairwise is a highly computational expensive algorithm.<br \/>\nTherefore a certain way of pruning is needed.<br \/>\nFirst the possible number of words per span should be limited and it makes sense to only pairwise score those mentions with the highest mention scores.<br \/>\nFurthermore one can neglect overlapping spans and only take a certain number of antecedents into account.<br \/>\nThis seems to be a lot of hyperparameters to tune and might eventually lead to throwing a way of gold training examples.<br \/>\nFortunately this is not the case.<br \/>\nFor spans which do not appear in the training data or whose antecedents do not contain the gold standard the model requires the introduction of a dummy span, which gets a score of zero.<br \/>\nFinally, all pairwise scored mentions should be clustered and represent now one entity.<\/p>\n<p>The authors present gains in F1 scores on the OntoNotes benchmark and hence reach state-of-the-art performance.<br \/>\nAdditionally the model allows to interpret the absence of coreference links and trace it back to either low mention scores or low mention ranking.<br \/>\nThe attention mechanism also nicely shows the contribution of the individual words in the span to the coreference decision.<\/p>\n<p><a id=\"orgbe92439\"><\/a><\/p>\n<h2>outlook<\/h2>\n<p>In the future additional information in the form of the output of a named entity recognizer or world knowledge could improve the models performance even more.<br \/>\nAnother paper which we want to mention here is &#8220;Event Coreference Resolution by Iteratively Unfolding Inter-dependencies among Events&#8221;.<br \/>\nIn addition to inter-document resolution of coreferences the authors tackle cross-document resolution and try to cluster mentions of real-world events.<\/p>\n<p><a id=\"org31c2240\"><\/a><\/p>\n<h2>resources<\/h2>\n<p><a href=\"https:\/\/arxiv.org\/abs\/1707.07045\">https:\/\/arxiv.org\/abs\/1707.07045<\/a><br \/>\n<a href=\"https:\/\/arxiv.org\/abs\/1707.07344\">https:\/\/arxiv.org\/abs\/1707.07344<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Table of Contents Coreference Resolution goal motivation ingredients steps outlook resources Coreference Resol [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[3642,3640],"tags":[],"class_list":["post-4331","post","type-post","status-publish","format-standard","hentry","category-ai-en","category-all-en"],"aioseo_notices":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/blog.themusio.com\/index.php?rest_route=\/wp\/v2\/posts\/4331","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.themusio.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.themusio.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.themusio.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.themusio.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4331"}],"version-history":[{"count":4,"href":"https:\/\/blog.themusio.com\/index.php?rest_route=\/wp\/v2\/posts\/4331\/revisions"}],"predecessor-version":[{"id":10845,"href":"https:\/\/blog.themusio.com\/index.php?rest_route=\/wp\/v2\/posts\/4331\/revisions\/10845"}],"wp:attachment":[{"href":"https:\/\/blog.themusio.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4331"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.themusio.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4331"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.themusio.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4331"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}