<title>Background</title> <p>Automatic semantic role labeling (SRL) is a natural language processing (NLP) technique that maps sentences to semantic representations, which can be useful for many NLP tasks (e.g. information extraction). With the advent of resources like FrameNet [##UREF##0##1##] and PropBank [##UREF##1##2##,##UREF##2##3##], this technique has had a flurry of activity in recent years. Much of this work has focused on the arguments of verbs, and because PropBank uses Wall Street Journal for its source documents, much of the work has been trained and evaluated on newswire text [##UREF##3##4##, ####UREF##4##5##, ##UREF##5##6##, ##UREF##6##7##, ##UREF##7##8##, ##UREF##8##9####8##9##].</p> <p>As a variety of research groups have reported success on these corpora, recent work has turned to transferring these results to different kinds of predicates and different genres of text. In this article, we show that automatic semantic role labeling can be transferred to the biomedical domain. Our goal is to accept as input sentences describing biological processes and infer structures like the following:</p> <p>(1) [<sub>PATIENT</sub> Bax] [<sub>PREDICATE</sub> translocation] from the [<sub>ORIGIN</sub> cytosol] to [<sub>DESTINATION</sub> mitochondria] leads to the subsequent formation....</p> <p>This predicate argument structure indicates, for example, that <italic>Bax </italic>has the PATIENT role in the <italic>translocation </italic>event, that is, <italic>Bax </italic>is the protein undergoing movement. In general, predicate argument structures characterize how different proteins and cellular components participate in biological events, and thus form the basis for understanding the text.</p> <p>Semantic role labeling systems from newswire domains need some adjustments to perform well on biomedical text. Biomedical text differs widely from the newswire text commonly used to train SRL systems, both in the style of the written text and the predicates involved. Predicates in newswire text are typically verbs, for example:</p> <p>(2) Four of the five [<sub>PREDICATE(VERB)</sub> surviving] workers [<sub>PREDICATE(VERB)</sub> have] asbestos-related diseases, [<sub>PREDICATE(VERB)</sub> including] three with recently [<sub>PREDICATE(VERB)</sub> diagnosed] cancer.</p> <p>Biomedical text often prefers nominal predicates, and light verbs like <italic>take </italic>or <italic>leave </italic>[##UREF##9##10##], which typically have little semantic content of their own. Example 3 shows a typical sentence, where there are only two verbs, <italic>left </italic>and <italic>abolished</italic>, and the former serves only as a light verb supporting the predicate <italic>unimpaired</italic>.</p> <p>(3) [<sub>PREDICATE(NOUN)</sub> Truncation] of up to 44 C-terminal amino acids from the putatively cytoplasmic C-terminal hydrophilic domain left transport function [<sub>PREDICATE(ADJ)</sub> unimpaired], but [<sub>PREDICATE(NOUN)</sub> deletion] of the adjacent STAS (sulfate transporter anti-sigma factor antagonist) domain [<sub>PREDICATE(VERB)</sub> abolished] function.</p> <p>The predicates used in biomedical text are also quite unlike those of other corpora. Predicates like <italic>endocytosis</italic>, <italic>exocytosis</italic>, <italic>internalize</italic>, <italic>traffic </italic>and <italic>translocate</italic>, though common in texts describing protein transport, are completely absent from both the FrameNet and PropBank data.</p> <p>Other researchers have explored the difficulties of adapting semantic role labeling technologies to new domains and have encountered the same two basic problems: differences in text style and differences in predicates. The CoNLL 2005 shared task [##UREF##10##11##] investigated semantic role labeling systems that were trained on the Wall Street Journal and tested on the Brown corpus. They found that "all systems experienced a severe drop in performance (about 10 F1 points)" when compared to their results on Wall Street Journal data, and attributed this drop to the poorer performance of sub-components like part-of-speech taggers and syntactic parsers. A similar performance drop was observed when semantic role labeling models were trained on nominal predicates. Pradhan et. al. [##UREF##11##12##] achieved an F-measure of only 63.9 when evaluating their models on nominal predicates from FrameNet and some manually annotated nominalizations from the Penn Chinese TreeBank. Jiang and Ng [##UREF##12##13##] achieved better results on the NomBank [##UREF##13##14##] corpus, but their F-measure was still only 72.7, more than 10 points below state of the art performance for verbs. Thus, these research efforts suggest that adapting semantic role labeling to biomedical text will offer some interesting challenges.</p> <p>BIOSMILE [##REF##17764570##15##] is the only SRL system of which we aware that targeted the biomedical domain. Our work significantly differs from BIOSMILE in both the data and algorithm that were used. The BIOSMILE system was trained on BioProp [##UREF##14##16##], a biomedical proposition bank semi-automatically annotated in the style of PropBank. BioProp, like other biomedical corpora of predicate argument structures, e.g. that of Kogan and colleagues [##REF##16779072##17##], considered only verbs, annotating 30 biomedical verbs in 500 abstracts. In contrast, the corpus used in this work includes both verbal and nominal forms (e.g. both <italic>translocates </italic>and <italic>translocation</italic>) for a total of 86 unique predicates (34 unique lemmas) describing protein transport events. Because BioProp followed PropBank style, their semantic roles were only allowed to match full syntactic units, while our data includes multi-word roles that are smaller than a traditional TreeBank style syntactic unit, a necessity for handling nominal predicates. Because of these many differences in data, and to evaluate methods that did not rely on computationally expensive syntactic parses, we explored an alternative to the syntactic constituent approach used by BIOSMILE, and trained a word-chunking model on our corpus.</p> <p>Our corpus consists of gene data from the National Library of Medicine (NLM). NLM began a Gene Indexing initiative on April 1, 2002, the goal of which was to link any article about the basic biology of a gene or protein to the corresponding entry in Entrez Gene [##UREF##15##18##], the National Center for Biotechnology Information's gene database. The result was an entry within Entrez Gene called a Gene Reference Into Function (GeneRIF) [##UREF##16##19##], which acts as an important textual source of the functional annotation of genes [##REF##16381840##20##,##REF##15661078##21##]. Our predicates and roles have been annotated over a subset of these GeneRIFs, for example:</p> <p>(4) IRS-3 expression blocked glucose/IGF-1 induced [<sub>PATIENT</sub> IRS-2] [<sub>PREDICATE</sub> translocation] from the [<sub>ORIGIN</sub> cytosol] to the [<sub>DESTINATION</sub> plasma membrane].</p> <p>GeneRIFs have been used in a variety of natural language processing projects on biomedical text, including projects to automate alerts for new findings [##REF##14728215##22##] and to extract summaries of PubMed/MEDLINE records [##UREF##17##23##, ####UREF##18##24##, ##UREF##19##25##, ##REF##17094227##26####17094227##26##]. Most relevant to the research at hand is [##REF##18237434##27##], which describes an information extraction system called OpenDMAP that combines pattern matching with domain specific ontologies to build applications capturing biomedical knowledge (e.g. protein transport).</p> <p>We used data similar to that of [##REF##18237434##27##], and focused in particular on predicates that describe protein transport. Protein transport is the biological process of moving proteins from one cellular component to another by various sorting mechanisms. For example, for extracellular signals to be transduced to the nucleus to activate specific genes, an essential step is translocating transcription factors into the nucleus. Understanding the mechanisms of protein transport has been a central theme in cell biology and has been studied for decades [##UREF##20##28##]. However, while natural language processing technologies have generally shown success in facilitating biomedical research [##REF##14990452##29##, ####REF##15383839##30##, ##REF##15608229##31##, ##REF##16103899##32####16103899##32##], there is currently very little work that has focused on applying NLP techniques to the protein transport domain.</p> <p>The GeneRIF data in our corpus were taken directly from the data used in developing and evaluating OpenDMAP (Open-source Direct Memory Access Parser) [##REF##18237434##27##], an open-source, ontology-driven concept analysis engine. Like OpenDMAP, our system can be applied to automatically extract protein transport information from texts. The main difference is that OpenDMAP used knowledge either directly found in its ontology or indirectly obtained by external programs. Thus, its overall performance depended on the output accuracy of those third-party applications. As reported in [##REF##18237434##27##], "A significant cause of errors in the OpenDMAP system as evaluated is incorrect identification of gene and protein names." For instance, a decrease of over 20% in recall of protein transport roles was reported in [##UREF##21##33##] when OpenDMAP was given automatically identified protein boundaries instead of human annotated boundaries. In contrast, only a slight (5%) decrease was shown in similar experiments presented in this work. We attribute the difference (5% vs. 20%) to the machine-learning models we employed, which were capable of recognizing proteins not found in the training data.</p> <p>In addition to the ontology-driven approach of OpenDMAP, there are other fundamentally different IE approaches that are currently used extensively in the biomedical domain, including co-occurrence approaches, heuristic and rule-based approaches, and syntactic analysis and machine-learning approaches [##REF##16418747##34##,##UREF##22##35##]. The semantic role labeling approach differs from these by focusing on the linguistically motivated semantic links between entities in a sentence. Such relations are common in most text, and have been shown to improve IE results dramatically [##UREF##23##36##], and so we chose to explore these methods here.</p>
<title>Methods</title> <title>Protein transport data</title> <p>A set of 1218 GeneRIFs was collected from two sources: GeneRIFs from genes known to be involved in protein transport (e.g. <italic>Src</italic>, a tyrosine kinase playing critical roles in signaling) and GeneRIFs containing predicates known to express transport (e.g. <italic>translocation </italic>or <italic>export</italic>). The predicates in each of these GeneRIFs were annotated with the roles AGENT, PATIENT, ORIGIN and DESTINATION by domain experts following the annotation guidelines of [##UREF##28##41##] and using the Knowtator annotation tool [##UREF##33##47##]. GeneRIFs that did not express protein transport (e.g. because they expressed some other type of transport like DNA transport) were discarded, resulting in a final data set of 837 GeneRIFs.</p> <p>Initially, this produced 1009 predicate annotations with 1803 labeled roles. However, in [##UREF##28##41##], if a predicate has a role containing a conjunction, e.g. <italic>HopO1-1, HopS1, and HopS2</italic>, the predicate would have been annotated three times, one for each conjoined element. This is a departure from most other semantic role labeling schemes, like PropBank and FrameNet, where the predicate would have been annotated only once, and the whole phrase <italic>HopO1-1, HopS1, and HopS2 </italic>would have been annotated as the argument. Having predicates annotated multiple times would require some substantial changes for most semantic role labeling architectures, which assume that each predicate needs to be visited only once to identify all of its roles. Thus, since the mapping from one form to the other was fairly straightforward, we decided to convert the annotations to the more widespread PropBank/FrameNet style of annotation. Table ##TAB##4##5## shows the statistics for the resulting corpus.</p> <title>Machine learning models</title> <p>Traditional approaches to semantic role labeling have generally fallen into one of two classes: syntactic constituent approaches and word chunking approaches. Syntactic constituent approaches [##UREF##3##4##, ####UREF##4##5##, ##UREF##5##6##, ##UREF##6##7##, ##UREF##7##8##, ##UREF##8##9####8##9##] look for predicate roles in the nodes of a syntactic parse tree, and have generally had the best performance on the standard test sets. Word chunking approaches [##UREF##27##40##,##UREF##34##48##] look for predicate roles in sequences of words, generally with somewhat lower performance than syntactic constituent approaches, but avoiding the heavy reliance on the expensive syntactic parsing process. To evaluate their appropriateness for protein transport role labeling, we consider each of these techniques in a little more depth.</p> <p>Syntactic constituent approaches to semantic role labeling work by asking whether each constituent in the syntactic tree is a role or not. For example, given the sentence:</p> <p>This protein, overexpressed in prostate cancer, shuttles between the cytoplasm and the nucleus</p> <p>A syntactic constituent role labeler would examine the syntactic tree in Figure ##FIG##0##1## and ask:</p> <p>• Is [<sub>DT</sub> This] a role of <italic>shuttles</italic>?</p> <p>• Is [<sub>NN</sub> protein] a role of <italic>shuttles</italic>?</p> <p>• Is [<sub>NP</sub> [<sub>DT</sub> This] [<sub>NN</sub> protein]] a role of <italic>shuttles</italic>?</p> <p>• ...</p> <p>A machine learning model is trained to answer such questions using features like the path of tree nodes between the predicate and the constituent in the tree, the voice of the predicate (active or passive), etc. The best of these systems are able to achieve precisions and recalls just above 80% [##UREF##7##8##,##UREF##8##9##]. This approach has also proven successful for identifying the semantic roles of some verbal predicates in biomedical data [##REF##17764570##15##]. However, this approach requires a computationally expensive syntactic parse, and relies on the boundaries of the syntactic parse constituents matching the boundaries of the semantic roles.</p> <p>Word chunking approaches to semantic role labeling avoid the need for a syntactic parse, and can be more flexible about the boundaries of semantic roles, though usually at some cost to performance [##UREF##8##9##,##UREF##27##40##,##UREF##34##48##,##UREF##35##49##]. The word-chunking formulation converts the semantic role labeling problem into a word classification problem by selecting appropriate labels for each word in the phrase. These labels are usually a combination of a B(eginning), I(nside) or O(utside) prefix that indicates the location of the word within the role, and a role suffix that indicates the type of the role containing the word. So for example, given the sentence <italic>Sales declined 10% to $251.2 million from $258.7 million</italic>, its words would be labeled as in Table ##TAB##5##6##. The best word chunking semantic role labelers acheived precisions and recalls around 70%, about 10 points below their constituent based counterparts, but with dramatically faster run times as no syntactic parse was required.</p> <title>Word-chunking classification models</title> <p>Though both constituent-based and word-chunking approaches could conceivably be applied to our protein transport data, we adopted the word-chunking approach for two reasons. First, a straightforward constituent based approach would have a maximum recall of 80% for our data set as 20% of our roles did not align to constituents. A word-chunking model does not have such a cap on its recall as it is not restricted by the TreeBank notion of phrase structure. (There may be ways to address this problem in the constituent based approach, but they would require substantial new extensions to the basic syntacitc constituent paradigm.) Second, while there is ongoing work to adapt syntactic parsers to biomedical text [##UREF##36##50##,##REF##17254351##51##], performance is still much lower than on newswire text. Thus it is useful to determine how far protein transport role labeling can get without relying on a syntactic parse.</p> <p>The basic word-chunking formulation of semantic role labeling looks much the same on our protein transport data as it did on newswire text. So, for example, in trying to identify the roles of <italic>translocation </italic>in the phrase <italic>to induce the nuclear translocation of NF-kappaB transcription factor</italic>, we attempt to label the words as in Table ##TAB##6##7##. The word <italic>nuclear </italic>begins (and ends) a DESTINATION role, the word <italic>NF-kappaB </italic>begins the PATIENT role that <italic>transcription </italic>and <italic>factor </italic>are inside of, and all other words are outside of protein transport roles.</p> <p>To train on such data, machine learning models try to assign to each word its corresponding chunk label. Of course, doing so requires some knowledge of the context (e.g. "have I already started a role or am I outside of one?") and so, as is common for word-chunking approaches, we considered a window around the word being classified. This meant that to classify a single word, the machine learning algorithm looked at both the features for that word, and the features and labels of some preceding and following words. For example, given the word and part of speech as features, and a window of one word on either side, the word <italic>transcription </italic>would be classified using the window of features and labels outlined in Table ##TAB##6##7##. Note that this windowing strategy allows the algorithm to recognize that when it sees the word <italic>transcription </italic>it is already inside of a PATIENT role. This kind of context is crucial for high quality word-chunking. We used an existing word-chunking package, YamCha [##UREF##26##39##], to train our models. YamCha is based on Support Vector Machine models and has performed well on a variety of similar tasks [##UREF##26##39##,##UREF##27##40##].</p> <title>Word-chunking features</title> <p>Of course, as in all machine learning problems, selecting an appropriate set of features for the task plays a critical role in the success of the algorithm. We began with the basic features used in the word-chunking model of [##UREF##27##40##], omitting only the features for people, organizations and locations which generally do not occur in GeneRIF data. This resulted in the feature set:</p> <p>• The text of the word</p> <p>• The text of the predicate</p> <p>• The part-of-speech (POS) of the word</p> <p>• The BIO tag for the phrase that includes the word</p> <p>• The brace tag indicating how many clauses start and end at the word</p> <p>To get a better idea of how these features work, consider the sentence:</p> <p>(13) BARD1 induces BRCA1 intranuclear foci formation by increasing RING-dependent [<sub>PATIENT</sub><sub>1 </sub>BRCA1] [<sub>DESTINATION</sub><sub>1 </sub>nuclear] [<sub>PREDICATE</sub><sub>1 </sub>import] and inhibiting [<sub>PATIENT</sub><sub>2 </sub>BRCA1] [<sub>ORIGIN</sub><sub>2 </sub>nuclear] [<sub>PREDICATE</sub><sub>2 </sub>export]</p> <p>Table ##TAB##7##8## shows the features for a few of the words in the sentence when the roles of the predicate <italic>import </italic>are being identified. Producing such feature values relied on the output of some existing sub-components:</p> <p>• Word stems are determined by a lookup table from the University of Pennsylvania of around 300,000 words [##UREF##37##52##].</p> <p>• Part-of-speech tags are identified by the MXPOST part-of-speech tagger [##UREF##38##53##].</p> <p>• Syntactic phrases are determined by a YamCha-based chunking system trained on the CoNLL 2000 [##UREF##39##54##] text chunking data</p> <p>• Clause boundaries are determined by a YamCha-based chunking system trained on the CoNLL 2001 [##UREF##40##55##] clause identification data.</p> <p>All of these sub-components were simple surface level processors that considered only things like the words themselves and orthographic features like capitalization and punctuation.</p> <title>Phrase-chunking features</title> <p>This basic set of features was small however, and missed some important characteristics of the task. To augment our feature space, we turned to Hacioglu et. al.'s phrase-chunking model [##UREF##27##40##]. The model itself was inappropriate for our task because, just as the syntactic constituent classification models, the phrase classification model considered phrases whose boundaries often did not align with our roles. The model's features, however, had a relatively straightforward translation to word-level features instead of phrase-level features and thus we modified them in that way for use with our model. To explain these new features, we again refer to the sentence from Example 13, repeated here as Example 14:</p> <p>(14) BARD1 induces BRCA1 intranuclear foci formation by increasing RING-dependent [<sub>PATIENT</sub><sub>1 </sub>BRCA1] [<sub>DESTINATION</sub><sub>1 </sub>nuclear] [<sub>PREDICATE</sub><sub>1 </sub>import] and inhibiting [<sub>PATIENT</sub><sub>2 </sub>BRCA1] [<sub>ORIGIN</sub><sub>2 </sub>nuclear] [<sub>PREDICATE</sub><sub>2 </sub>export]</p> <p>The phrase-chunking features included all of the word-chunking features and the following additional features:</p> <p>• 2, 3, and 4 character suffixes of the word, e.g. the suffixes for <italic>nuclear </italic>are <italic>-ar</italic>, <italic>-ear </italic>and <italic>-lear</italic>.</p> <p>• The stem of the predicate, e.g. the stem of <italic>imports </italic>would be <italic>import</italic></p> <p>• The part-of-speech (POS) of the predicate, e.g. the POS of <italic>nuclear </italic>is JJ</p> <p>• The number of predicates in the sentence, e.g. there are 2 predicates, <italic>import </italic>and <italic>export</italic>.</p> <p>• The part-of-speech of the word before the predicate, e.g. the predicate <italic>import </italic>is preceded by the part-of-speech JJ (the POS of the word <italic>nuclear</italic>).</p> <p>• The part-of-speech of the word after the predicate, e.g. the predicate <italic>import </italic>is followed by the part-of-speech CC (the POS of the word <italic>and</italic>).</p> <p>• The two phrase types preceding the predicate, e.g. the noun phrase including <italic>import </italic>is preceded by a PP (prepositional phrase), <italic>by</italic>, and a VP (verb phrase), <italic>increasing</italic>.</p> <p>• The two phrase types following the predicate, e.g. the noun phrase including <italic>import </italic>is followed by a VP (verb phrase), <italic>inhibiting</italic>, and a NP (noun phrase), <italic>BRCA1 nuclear export</italic>.</p> <p>• The location of the word relative to the predicate, e.g. <italic>nuclear </italic>is BEFORE the predicate <italic>import </italic>and <italic>inhibiting </italic>is AFTER the predicate.</p> <p>• The distance between the predicate and the word in number of phrases, e.g. <italic>inhibiting </italic>is 1 phrase away (1 VP) from the predicate <italic>import</italic>, and <italic>export </italic>is 2 phrases away (1 VP and 1 NP) from the predicate.</p> <p>• The distance between the predicate and the word in number of verb phrases, e.g. both <italic>inhibiting </italic>and <italic>export </italic>are 1 VP away from the predicate <italic>import</italic>.</p> <p>• The phrasal path between the predicate and the word, e.g. the path from the second <italic>BRCA1 </italic>to <italic>import </italic>is NNP &lt; NP &lt; NN (it is in the same NP as <italic>import</italic>), and the path from <italic>import </italic>to <italic>inhibiting </italic>is NN&gt;NP &gt; VP &gt; VBG (it is one NP and one VP away from <italic>import</italic>).</p> <p>• The clause boundaries between the predicate and the word, e.g. there is a single open clause boundary, '(', between <italic>by </italic>and the predicate <italic>import</italic>.</p> <p>• The clause boundaries between the sentence boundary and the word, e.g. there are two open clause boundaries, '((', between <italic>BRCA1 </italic>and the beginning of the sentence.</p> <title>Protein-transport features</title> <p>Preliminary experiments (carried out as cross-validations on the training data) showed that our models were having difficulties with a few different areas of our data: the boundaries of protein names, conjoined predicates and arguments tied to a predicate through coreference.</p> <p>We noticed early on that our models were having trouble determining when a phrase immediately preceding a predicate should be identified as a PATIENT. For example, our early models identified <italic>GLUT4 requires </italic>instead of <italic>GLUT4 </italic>as the PATIENT in Example 15, and couldn't find any PATIENT at all in Example 16.</p> <p>(15) These results suggest that [<sub>PATIENT</sub> GLUT4] requires [<sub>PREDICATE</sub> translocation]...</p> <p>(16) ... involved in [<sub>PATIENT</sub> eNOS] [<sub>PREDICATE</sub> translocation]...</p> <p>The system had learned a strategy that identified as the PATIENT everything from the last "proper noun" up to the predicate. In these two examples, the part-of-speech tagger identified only GLUT4 as a proper noun, and so not only did the system incorrectly include <italic>requires </italic>as part of the PATIENT in Example 15, but it also failed to include the PATIENT <italic>eNOS </italic>in Example 16. These errors indicated that our models were having trouble identifying the boundaries of protein names.</p> <p>Our models were also having trouble with conjoined predicates, particularly when an argument was present for the first but elided for the second. So, for instance, in Example 17, <italic>protein </italic>is the PATIENT of both <italic>folding </italic>and <italic>translocation</italic>, and in Example 18, <italic>Tir </italic>is the PATIENT of both <italic>secretion </italic>and <italic>translocation</italic>. In both of these examples, our early models failed to identify <italic>protein </italic>and <italic>Tir </italic>as PATIENT roles of the <italic>translocation </italic>predicates.</p> <p>(17) ... for ERdj5 in [<sub>PATIENT</sub> protein] folding and [<sub>PREDICATE</sub> translocation]...</p> <p>(18) ... for efficient [<sub>PATIENT</sub> Tir] secretion and [<sub>PREDICATE</sub> translocation]...</p> <p>Though our models were given a window of features around the word classified, this window was generally no more than two words before of after the word. (We experimented with larger windows, but these models only performed worse.) Thus words like <italic>protein </italic>and <italic>Tir </italic>above were too distant from the predicate to be considered as arguments, and so our models failed on them.</p> <p>Finally, our models had trouble with the annotation style of [##UREF##28##41##] in that it annotates some roles that are tied to the predicate only through a coreference chain. Example 19 shows such a role.</p> <p>(19) a rapid activation of the [<sub>PATIENT</sub> acid sphingomyelinase] correlating with its microtubule- and microfilament-mediated [<sub>PREDICATE</sub> translocation]</p> <p>In this example, the predicate <italic>translocation </italic>is contained within the prepositional phrase <italic>with its... translocation</italic>. PropBank-style annotation would thus likely annotate <italic>its </italic>as the PATIENT of <italic>translocation</italic>. However, the annotation style of [##UREF##28##41##] allows for implicitly following up the coreference chain to conclude that <italic>its </italic>actually refers to <italic>acid sphingomyelinase</italic>, and then annotating <italic>acid sphingomyelinase </italic>as the PATIENT instead. These sorts of annotation decisions typically distance the argument from its predicate and make it difficult for our system to find the role.</p> <p>To address these three issues – unidentified proteins, conjoined predicates and coreference chains – we introduced the following additional features:</p> <p>• A set of orthographic features that capture some of the irregularities of protein names. These included:</p> <p>- The capitalization class of the word; one of INITIAL-UPPER, ALL-UPPER, ALL-LOWER, MIXED-UPPER-LOWER or OTHER</p> <p>- The numeric class of the word; one of YEAR-DIGITS, DIGITS, ALPHANUMERIC, SOME-DIGITS, ROMAN-NUMERAL or OTHER</p> <p>- The punctuation class of the word; one of PUNCT-ONLY, INITIAL, POSSIBLE-INITIAL, ACRONYM, or HAS- plus one or more of DOT, DASH, SLASH or COMMA for each contained in the word.</p> <p>• The part of speech tag output by MedPost [##REF##15073016##56##], a part of speech tagger trained on biomedical data, and therefore less likely to perform poorly when encountering protein names.</p> <p>• A protein BIO-chunk label of the word, i.e. B_PROTEIN, I_PROTEIN or o. We examined both manually annotated proteins, to give us an idea of the maximum possible performance, and proteins annotated automatically by ABNER [##REF##15860559##57##], a model based on conditional random fields and orthographic and gazetteer-based features.</p> <p>• A feature indicating whether or not the word was in a base-phrase conjoined with the base-phrase of the predicate, and which conjunction was conjoining them, e.g. <italic>and </italic>or a comma.</p> <p>• A feature indicating whether or not the word was part of the last protein before a pronoun. This is essentially a poor-man's coreference resolution scheme.</p> <p>In combination with the Word-Chunking features and the Phrase-Chunking features discussed above, these features served as the basis for all our machine learning experiments on our GeneRIF protein transport data.</p>
<title>Results</title> <title>Protein transport data analysis</title> <p>We constructed a corpus of 837 GeneRIFs annotated with protein transport predicates and their AGENT, PATIENT, ORIGIN and DESTINATION roles. (See Methods section for details.) There were some interesting differences between this protein transport data and the more traditional semantic role data of resources like FrameNet and PropBank. Of course, as discussed above, there were a variety of predicates in the protein transport data which never occurred in the kind of newswire text that is common in FrameNet and PropBank. But in addition to these basic differences in predicate inventories, there were some structural differences in the data. About 85% of predicates in the protein transport data were nouns, with only 15% verbs. For comparison, the test data for FrameNet semantic role labeling in SensEval-3 [##UREF##24##37##] was about 40% nouns, 40% verbs and 20% adjectives. So protein transport predicates have a much greater bias toward nominal forms.</p> <p>These nominal predicates introduce some additional challenges to semantic role labeling systems. First, many semantic relations are expressed by noun compounding, where many of the syntactic cues that were useful for verbs are unavailable. For example, there is often no subject/object distinction for nouns, so that a two-noun compound can be formed just as easily using the verbal equivalent's subject, object or prepositional object. So for example, given the phrase <italic>The transporter translocates GLUT-4 to the nucleus</italic>, paraphrases using the nominalization <italic>translocation </italic>could look like Example 5, Example 6 or Example 7.</p> <p>(5) [<sub>AGENT</sub> transporter] translocation</p> <p>(6) [<sub>PATIENT</sub> GLUT-4] translocation</p> <p>(7) [<sub>DESTINATION</sub> nuclear] translocation</p> <p>Nominal predicates are also more difficult due to their mismatch with commonly available syntactic tree structures. The Penn TreeBank [##UREF##25##38##] gives a very flat structure to noun phrases. For example, the phrase <italic>fatty acid transport protein translocation </italic>would appear as a single NP with no internal structure, even though it contains an embedded nominal role, <italic>fatty acid transport protein</italic>:</p> <p>(8) [NP [<sub>PATIENT</sub> fatty acid transport protein] [<sub>PREDICATE</sub> translocation]]</p> <p>In fact, in our transport predicate data, about 20% of roles look like this – there is no single syntactic constituent that matches their boundaries. For comparison, in the Propbank data, only 2% of roles did not correspond to a single constituent, in the NomBank data 5% did not match, and in the FrameNet data 15% did not match. Note that this is likely a major difference between our corpus and the verb-oriented BIOSMILE corpus. Thus, the protein transport data imposes a number of challenges on semantic role labeling: a much greater bias towards nominal predicates, fewer syntactic cues to help identify the roles, and a large mismatch between the role boundaries and the syntactic constituent boundaries. These difficulties need to be addressed when designing a semantic role labeling method for protein transport data.</p> <title>Experimental results</title> <p>For the purposes of our machine learning experiments, 200 GeneRIFs were selected at random from our protein transport corpus and reserved as the test set, to be used only for the final evaluation. The remaining 637 GeneRIFs were used to train machine learning models based on the word-chunking machine learning approach discussed in the Methods section. YamCha [##UREF##26##39##], our SVM-based machine learning algorithm, requires a number of different parameters to be specified: the cost of misclassification, the degree of the polynomial and the width of the feature window. To determine the best set of these parameters, we first ran a number of cross-validations on the training set, varying each parameter over a number of possible values, and checking the cross-validation performance. For the Word-Chunking and Protein-Transport models, the best cost was 10.0, the best polynomial degree was 2, and the best window size was 2 words before and after. For the Phrase-Chunking model, the best cost was 0.1, the best polynomial degree was 1, and the best window size was 2 words before and after.</p> <p>These parameters were then used to train the models on the full 637 GeneRIFs in the training data. We trained models on the following feature sets:</p> <title>Word-Chunking</title> <p>The basic Word-Chunking Features of [##UREF##27##40##]. (See the Methods section for details.)</p> <title>Phrase-Chunking</title> <p>The Word-Chunking features plus the Phrase-Chunking Features derived from the phrase-chunking model of [##UREF##27##40##]. (See the Methods section for details.)</p> <title>Protein-Transport</title> <p>The Phrase-Chunking features plus the features inspired by the analysis of the protein transport data: the orthographic features, the MedPost part of speech tags, the protein BIO chunk labels, and the conjunction and coreference features. (See the Methods section for details.)</p> <p>We evaluate these models in terms of precision, recall and F-measure:</p> <p></p> <p>Precision is the number of roles the system identified correctly divided by the number of roles the system predicted. Recall is the number of roles the system identified correctly divided by the number of roles that were present in manually annotated data. <italic>F</italic><sub>1</sub>-measure (often abbreviated simply as F-measure) is defined as the harmonic mean of precision and recall.</p> <p>The task can also be viewed as a two step process in which boundaries are first identified and then role classes are labeled. Under this view, the models are evaluated in terms of unlabeled precision, unlabeled recall and labeled accuracy. Unlabeled precision and recall are just like precision and recall but ignore the label type (e.g. AGENT or PATIENT) and only check that the boundaries of the roles are correct. Labeled accuracy reports, for the roles whose boundaries were correctly identified, the percent that were assigned the proper label type.</p> <p>Table ##TAB##0##1## gives precision, recall, F-measure and labeled accuracy values for our models when evaluated on the 200 GeneRIFs reserved as our test set. The model trained using only the simple word-chunking features was able to achieve 79.7% precision and 64.4% recall, reasonably good results given that this model relied on only 5 simple features. Adding in all the features derived from the phrase-chunking model raised model performance up to 81.0% precision and 71.9% recall, indicating that our translation of the Hacioglu [##UREF##27##40##] phrase chunking features to word chunking features was effective. The model that incorporated all the protein transport features in addition to the word and phrase features achieved 87.6% precision and 79.0% recall, a more than 6% gain in both precision and recall over the best baseline model. Since some of the protein transport features were derived from manually annotated protein annotations, it was also useful to examine how using automatic protein annotations affected performance. The last row of Table ##TAB##0##1## shows these numbers. Using the automatic protein annotations from ABNER resulted in less than a 1% drop in precision, but in almost a 5% drop in recall. These results were still higher than the baseline word-chunking and phrase-chunking models, but it was clear that the protein-based features were playing a strong role in the model, and having lower quality protein annotations resulted in lower quality semantic roles.</p>
<title>Discussion</title> <p>The high performance of our final model indicated that existing semantic role labeling techniques can be adapted to domains such as protein transport by adding a few carefully chosen domain-relevant features. Performance dropped slightly when using automatically identified protein boundaries, but as automatic protein identification systems like ABNER improve, we should see similar improvement in the performance of our role labeler.</p> <title>Analysis by role type</title> <p>One of the interesting characteristics of all our models was that when our models were able to find a role, they typically had little trouble identifying the type of that role – labeled accuracy was 98% and higher for all models. This high classification accuracy can probably be attributed to two factors. First, the annotation style dictated that the AGENT and PATIENT roles were always proteins, while ORIGIN and DESTINATION roles were always non-proteins. Thus while occasional confusions between, say, ORIGIN and DESTINATION might have been possible, confusions between, say, AGENT and DESTINATION should have been extremely unlikely. Second, these four roles, particularly in the protein transport domain, appear in a somewhat limited number of forms. For example, work on a related corpus suggested that only five OpenDMAP-style patterns were required for good performance [##REF##18237434##27##]. As can be seen from our evaluation results, our machine learning model performed like a set of high precision patterns would have – with very few confusions, and with precision substantially higher than recall.</p> <p>Thus, the main issue for our models was not in distinguishing one role from another, but in finding the roles in the first place. To get an idea of how difficult the different types of roles were to identify, we calculated precision, recall and F-measure on each role type for our best model, the model using the Protein-Transport feature set with manually annotated protein boundaries. The results are shown in Table ##TAB##1##2##. Our models found only one of the three AGENT examples in our testing data due to data sparsity issues – AGENT roles made up less than 1% of the roles in our protein transport predicates. AGENT roles were also harder because they tended to be further from the predicate. On the average, less than 50% of AGENT roles were within three words of the predicate, while more than 75% of PATIENT, ORIGIN and DESTINATION roles were within this window. Roles that were closer to the predicate were easier for our system to identify because they appeared within the word window our models considered during classification.</p> <p>Our models performed best on DESTINATION roles, probably because DESTINATION roles appeared in fewer different forms. For example, the pattern <italic>nuclear </italic>&lt;predicate&gt; accounted for about 30% of all DESTINATION roles. To further elaborate on this kind of analysis, we calculated seen/unseen statistics for each role phrase. That is, we calculated separate precision, recall and F-measure values for the role phrases that appeared in both the training data and the test data, and for the role phrases that appeared only in the test data. Table ##TAB##2##3## shows these statistics. Though all roles see some drop in performance from seen roles to unseen roles, the most dramatic drops are for AGENT roles, where unseen AGENT roles are <italic>never </italic>identified, and ORIGIN roles, where there is a 75 point drop in F-measure (from 90.4 to 15.4). As discussed above, the difficulties with AGENT roles are almost certainly due to their sparsity, but the difficulties with ORIGIN roles suggest this class of roles is intrinsically more difficult. These results indicate that some additional feature engineering may be required to better characterize ORIGIN roles. Fortunately, most ORIGIN roles were seen in the training data, and only 13.3% of ORIGIN roles are of this more difficult type.</p> <title>Analysis of genre issues</title> <p>To determine how well our additional features addressed the issues particular to the the biomedical genre, we checked model performance for some different predicate types. In particular, we examined how model performance varied with the part of speech of the predicate (nominal predicates are much more common in our data), and with the domain from which the predicate was drawn. Table ##TAB##3##4## shows the results of this analysis. With just the basic Phrase-Chunking feature set, F-measure for verbal predicates, which make up only 20.8% of our data, is dramatically lower than for nominal predicates: 58.1 for verbs compared with 70.7 for nouns. Adding in the Protein-Transport features both increases overall performance and substantially reduces this disparity – the model achieves an F-measure of 80.6 for nominal predicates and an F-measure of 76.7 for verbal predicates. Thus, the Protein-Transport features help to address the difficulties of the increased number of nominal predicates.</p> <p>Analyzing general differences in text style from one domain to another is more difficult, but to approximate it, we considered two classes of predicates: predicates that occurred somewhere in the Wall Street Journal section of the Penn TreeBank (e.g. <italic>delivery</italic>, <italic>move </italic>and <italic>released</italic>), and predicates which were only observed in our GeneRIF data (e.g. <italic>efflux</italic>, <italic>relocates </italic>and <italic>translocation</italic>). Table ##TAB##3##4## shows that moving from the Phrase-Chunking features to the full Protein-Transport features results in at least a 10 point gain in F-measure for both types of predicates. Interestingly, however, our additional features seem to be more helpful for Wall Street Journal predicates than GeneRIF-only predicates – Wall Street Journal predicates get a 15 point boost in F-measure, from 67.9 to 83.2, while GeneRIF-only predicates get only a 10 point boost, from 68.0 to 78.6. These results suggest that while our features are capturing many of the important characteristics of the GeneRIF domain, there may still be room for features tailored to the peculiarities of protein transport predicates.</p> <title>Analysis of model errors</title> <p>To get a better idea exactly where future work on feature engineering should focus, we took a look at the mistakes our best model was making and identified a few broad classes of errors. About 40% of the model's errors could be attributed to trouble with roles that required tracing a coreference chain to find the argument. As discussed under Protein-Transport Feature in the Methods section, the scheme of [##UREF##28##41##] allows roles to be annotated in distant parts of the sentence if a coreference chain links the predicate and the distant argument. So for instance, <italic>p53 </italic>in Example 9 and <italic>Daxx </italic>in Example 10 are marked as arguments instead of the closer pronoun <italic>its</italic>. Our system missed the distant PATIENT roles in both of these examples.</p> <p>(9) Serine 392 exerts important effects upon [<sub>PATIENT</sub> p53] stability via the inhibition of its [<sub>ORIGIN</sub> nuclear] [<sub>PREDICATE</sub> export] mechanism.</p> <p>(10) Tryptophan 521 and serine 667 residues of [<sub>PATIENT</sub> Daxx] regulate its [<sub>ORIGIN</sub> nuclear] [<sub>PREDICATE</sub> export] during glucose deprivation</p> <p>Another 20% of the errors were due to boundary mismatches, where our system predicted shorter or longer arguments. Most such errors appeared to be due to errors in our syntactic chunkers and clause chunkers, which were trained on Wall Street Journal text, not biomedical text. In Example 11, <italic>substrate </italic>was chunked as a verb phrase instead of as part of a noun phrase, and so our system identified only <italic>1 </italic>as a PATIENT, instead of the full <italic>Insulin receptor substrate 1</italic>.</p> <p>(11) [<sub>PATIENT</sub> Insulin receptor substrate 1] [<sub>PREDICATE</sub> translocation] to the [<sub>DESTINATION</sub> nucleus]</p> <p>Finally, for about 15% of the errors it looked like having a complete syntactic parse would have helped. In these errors, one role was often separated from the predicate by something like an appositive. In Example 12, the PATIENT <italic>protein </italic>was missed because it was separated from the predicate by <italic>overexpressed in prostate cancer</italic>.</p> <p>(12) This [<sub>PATIENT</sub> protein], overexpressed in prostate cancer, [<sub>PREDICATE</sub> shuttles] between the cytoplasm and the nucleus.</p> <p>Figure ##FIG##0##1## shows that with a syntactic parse, <italic>protein </italic>is the head noun of the predicate's NP complement, essentially only two constituents away, compared to a distance of six words (including punctuation) when not using a syntactic parse.</p> <p>These three classes of errors accounted for about 75% of the errors made by our system. They suggest that future research on protein transport roles could benefit by including features derived from coreference systems [##REF##18237434##27##,##UREF##29##42##, ####UREF##30##43##, ##UREF##31##44####31##44##] to better link predicates with their distant arguments, by training some of our intermediate components like syntactic and clause chunkers on biomedical text, and by including some features extracted from full syntactic parses.</p> <title>Comparison to the OpenDMAP method</title> <p>Unfortunately, we cannot directly compare the numbers here to those of OpenDMAP, which reported precision of 0.75 and a recall of 0.49 [##REF##18237434##27##]. First, they evaluated only the predicate <italic>translocation </italic>while many other transport predicates (e.g. <italic>import</italic>) are considered in this work. Second, they calculated precision and recall at the sentence level instead of the individual role level, and included identifying the predicate as part of the task. Third, different data preprocessing strategies were used. For example, conjunctions in GeneRIFs were handled differently (see details in the Result Section). Although we cannot perform head-to-head comparison, we would like to point out that the two approaches are potentially complementary to one another. The OpenDMAP system is primarily based on curated ontologies and patterns that make it capable of assigning identified roles with high precision. However, automatically recognizing biomedical concepts (e.g. gene/proteins) remains challenging by current technologies. The statistical SRL system presented here provides a potential remedy because of its robustness in identifying roles in text. We are going to explore potential synergies between the two systems in the future, but this is beyond the scope of this work.</p> <title>General limitations</title> <p>While the performance of our protein transport role labeling system is quite good, it is worth reflecting on a few of its limitations. First, our systems used word-chunking methods instead of constituent classification methods (and some of the benefits and drawbacks of this choice are discussed in the Methods section). In general, word-chunking models were useful for our data because they resulted in a much faster system with the ability to identify roles that were smaller than typical syntactic tree constituents. However, as noted in the Analysis of model errors section above, some distant roles may be more easily identified using a syntactic tree, and therefore may be more tractable for constituent classification methods.</p> <p>Another limitation of this study was that our models were trained and evaluated on protein transport predicates, which are not fully representative of all the different predicates in biomedical text. As a consequence of this, the AGENT role was almost completely absent from our data (as discussed in the Analysis by Role Type section above). It is quite possible that other biomedical predicates use AGENT roles much more often, and the system would have to learn to better distinguish between AGENT and PATIENT. In newswire verbs, AGENT and PATIENT roles were among the easiest to identify [##UREF##7##8##,##UREF##32##45##], but since biomedical predicates are often nouns, it may be necessary to introduce some additional features to make these distinctions.</p> <p>Finally, our approach showed that model performance could be improved substantially by introducing some domain specific features. However, the need for these features indicates that adapting semantic role labeling methods to the biomedical domain is more work than just building a corpus and retraining an existing model. In our case, the additional features were mostly based on biomedical part of speech and named entity (protein) tags, which we used in addition to the standard newswire tags. Thus, our results suggest that to build successful role labeling systems for new domains, not only is it necessary to create an appropriate corpus and train a new machine learning model, but it is also necessary to train new models for all subcomponents (e.g. part of speech taggers, named entity taggers, etc.) and include the outputs of these models as additional features.</p> <p>Despite these limitations, the current level of performance of our semantic role labeling system provides two important facilities to the research community. First, semantic roles identified with reasonable precision can be used to increase the efficiency of manual curation efforts, by providing a small set of relevant passages that curators may consider for entry into their databases. Second, even imperfect semantic role labeling performance may be of use to downstream components that know how to integrate noisy data. For example, [##REF##18412966##46##] showed that including noisy information based only on word co-occurrence statistics substantially improved the quality and coverage of protein-protein interaction networks. Thus, we expect that our semantic role labeling system, which achieved precisions as high as 87.6%, should be a useful sub-component for a variety of information extraction tasks.</p>
<title>Conclusion</title> <p>We have presented a model for identifying the semantic roles of protein transport predicates. A corpus was collected of GeneRIFs describing biological processes where proteins were moved from one cellular component to another. The predicates describing these processes, both nouns and verbs, were annotated for their semantic roles. This corpus then served as the basis for several machine learning experiments.</p> <p>We explored word-chunking approaches to semantic role labeling, both to avoid the need for a computationally expensive syntactic parse, and because the traditional Penn TreeBank notions of syntactic constituent boundaries mismatched badly with the annotated protein transport roles. Thus, we trained support vector machine classifiers to classify words as being at the beginning, inside or outside of a protein transport role (AGENT, PATIENT, ORIGIN or DESTINATION). We trained these models using the features of previous word-chunking models, features adapted from other types of models, and features derived from analysis of our protein transport data.</p> <p>In the end, our models were able to achieve a 87.6% precision and 79.0% recall using manually annotated protein boundaries, and 87.0% precision and 74.5% recall using automatic ones. Our protein transport models outperformed models trained on only the traditional word-chunking and phrase-chunking features, indicating that the new features we engineered for the biomedical domain were effective in addressing some of the domain differences. And the relatively small drop in performance when using automatically identified proteins suggests that our models are relatively robust to imperfect features, which is a necessity for working with real-world biomedical langauge processing systems. Analysis of our models suggested that future research should focus on including features derived from coreference resolution systems, improving the performance on biomedical text of components like syntactic chunkers and protein identifiers, and exploring features based on full syntactic parses.</p>
<p>This is an Open Access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/2.0"/>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</p> <title>Background</title> <p>Automatic semantic role labeling (SRL) is a natural language processing (NLP) technique that maps sentences to semantic representations. This technique has been widely studied in the recent years, but mostly with data in newswire domains. Here, we report on a SRL model for identifying the semantic roles of biomedical predicates describing protein transport in GeneRIFs – manually curated sentences focusing on gene functions. To avoid the computational cost of syntactic parsing, and because the boundaries of our protein transport roles often did not match up with syntactic phrase boundaries, we approached this problem with a word-chunking paradigm and trained support vector machine classifiers to classify words as being at the beginning, inside or outside of a protein transport role.</p> <title>Results</title> <p>We collected a set of 837 GeneRIFs describing movements of proteins between cellular components, whose predicates were annotated for the semantic roles AGENT, PATIENT, ORIGIN and DESTINATION. We trained these models with the features of previous word-chunking models, features adapted from phrase-chunking models, and features derived from an analysis of our data. Our models were able to label protein transport semantic roles with 87.6% precision and 79.0% recall when using manually annotated protein boundaries, and 87.0% precision and 74.5% recall when using automatically identified ones.</p> <title>Conclusion</title> <p>We successfully adapted the word-chunking classification paradigm to semantic role labeling, applying it to a new domain with predicates completely absent from any previous studies. By combining the traditional word and phrasal role labeling features with biomedical features like protein boundaries and MEDPOST part of speech tags, we were able to address the challenges posed by the new domain data and subsequently build robust models that achieved F-measures as high as 83.1. This system for extracting protein transport information from GeneRIFs performs well even with proteins identified automatically, and is therefore more robust than the rule-based methods previously used to extract protein transport roles.</p>
<title>Authors' contributions</title> <p>SB and ZL wrote most of this paper. SB designed and trained the machine learning models, and performed the experimental evaluations. ZL collected the GeneRIF data and participated in the experimental designs. JHM and LH helped to guide and advise the project. All authors read and approved the final manuscript.</p> <title>Appendix: list of protein transport role examples</title> <p>The following are all the examples of protein transport predicates and their roles given in the article.</p> <p>(1) [<sub>PATIENT</sub> Bax] [<sub>PREDICATE</sub> translocation] from the [<sub>ORIGIN</sub> cytosol] to [<sub>DESTINATION</sub> mitochondria] leads to the subsequent formation. ...</p> <p>(3) [<sub>PREDICATE(NOUN)</sub> Truncation] of up to 44 C-terminal amino acids from the putatively cytoplasmic C-terminal hydrophilic domain left transport function [<sub>PREDICATE(ADJ)</sub> unimpaired], but [<sub>PREDICATE(NOUN)</sub> deletion] of the adjacent STAS (sulfate transporter anti-sigma factor antagonist) domain [<sub>PREDICATE(VERB)</sub> abolished] function.</p> <p>(4) IRS-3 expression blocked glucose/IGF-1 induced [<sub>PATIENT</sub> IRS-2] [<sub>PREDICATE</sub> translocation] from the [<sub>ORIGIN</sub> cytosol] to the [<sub>DESTINATION</sub> plasma membrane].</p> <p>(9) Serine 392 exerts important effects upon [<sub>PATIENT</sub> p53] stability via the inhibition of its [<sub>ORIGIN</sub> nuclear] [<sub>PREDICATE</sub> export] mechanism.</p> <p>(10) Tryptophan 521 and serine 667 residues of [<sub>PATIENT</sub> Daxx] regulate its [<sub>ORIGIN</sub> nuclear] [<sub>PREDICATE</sub> export] during glucose deprivation</p> <p>(11) [<sub>PATIENT</sub> Insulin receptor substrate 1] [<sub>PREDICATE</sub> translocation] to the [<sub>DESTINATION</sub> nucleus]</p> <p>(12) This [<sub>PATIENT</sub> protein], overexpressed in prostate cancer, [<sub>PREDICATE</sub> shuttles] between the cytoplasm and the nucleus.</p>
<title>Acknowledgements</title> <p>SB worked under an appointment to the DHS Scholarship and Fellowship Program, administered by ORISE through an interagency agreement between DOE and DHS. ORISE is managed by ORAU under DOE contract number DE-AC05-06OR23100. ZL and LH worked under National Library of Medicine grant 5R01LM008111-03 and R01LM009254. ZL was also supported in part by the Intramural Research Program of the NIH, National Library of Medicine. Computer time was provided by NSF ARI Grant #CDA-9601817, NSF MRI Grant #CNS-0420873, NASA AIST grant #NAG2-1646, DOE SciDAC grant #DE-FG02-04ER63870, NSF sponsorship of the National Center for Atmospheric Research, and a grant from the IBM Shared University Research (SUR) program. All opinions expressed in this article are the authors' and do not necessarily reflect the policies and views of the sponsors.</p>
<fig position="float" id="F1"><label>Figure 1</label><caption><p><bold>Example syntactic tree</bold>. This figure shows the syntactic tree for the phrase <italic>This protein, overexpressed in prostate cancer, shuttles between the cytoplasm and the nucleus</italic>.</p></caption></fig>
<table-wrap position="float" id="T1"><label>Table 1</label><caption><p>Model performance by feature set.</p></caption><table frame="hsides" rules="groups"><thead><tr><td/><td align="center" colspan="3">Labeled</td><td align="center" colspan="2">Unlabeled</td><td align="center">Labeled</td></tr><tr><td/><td colspan="3"><hr/></td><td colspan="2"><hr/></td><td colspan="1"><hr/></td></tr><tr><td/><td align="center">Precision</td><td align="center">Recall</td><td align="center">F-measure</td><td align="center">Precision</td><td align="center">Recall</td><td align="center">Accuracy</td></tr></thead><tbody><tr><td align="left">Word-Chunking</td><td align="center">79.7</td><td align="center">64.4</td><td align="center">71.3</td><td align="center">80.1</td><td align="center">64.7</td><td align="center">99.6</td></tr><tr><td align="left">Phrase-Chunking</td><td align="center">81.0</td><td align="center">71.9</td><td align="center">76.2</td><td align="center">81.9</td><td align="center">72.7</td><td align="center">98.9</td></tr><tr><td align="left">Protein-Transport</td><td align="center">87.6</td><td align="center">79.0</td><td align="center">83.1</td><td align="center">87.9</td><td align="center">79.2</td><td align="center">99.7</td></tr><tr><td align="left">Protein-Transport (ABNER)</td><td align="center">87.0</td><td align="center">74.5</td><td align="center">80.3</td><td align="center">87.3</td><td align="center">74.8</td><td align="center">99.7</td></tr></tbody></table></table-wrap> <table-wrap position="float" id="T2"><label>Table 2</label><caption><p>Model performance by role type.</p></caption><table frame="hsides" rules="groups"><thead><tr><td/><td align="center">Precision</td><td align="center">Recall</td><td align="center">F-measure</td><td align="center">% of Roles</td></tr></thead><tbody><tr><td align="left">AGENT</td><td align="center">100.0</td><td align="center">33.3</td><td align="center">50.0</td><td align="center">0.8</td></tr><tr><td align="left">PATIENT</td><td align="center">86.5</td><td align="center">74.4</td><td align="center">80.0</td><td align="center">51.7</td></tr><tr><td align="left">ORIGIN</td><td align="center">82.9</td><td align="center">75.6</td><td align="center">79.1</td><td align="center">11.7</td></tr><tr><td align="left">DESTINATION</td><td align="center">90.3</td><td align="center">87.7</td><td align="center">89.0</td><td align="center">35.8</td></tr></tbody></table></table-wrap> <table-wrap position="float" id="T3"><label>Table 3</label><caption><p>Model performance by seen vs. unseen.</p></caption><table frame="hsides" rules="groups"><thead><tr><td/><td align="center">Precision</td><td align="center">Recall</td><td align="center">F-measure</td><td align="center">%</td></tr></thead><tbody><tr><td align="left">Seen roles</td><td align="center">97.7</td><td align="center">88.9</td><td align="center">93.1</td><td align="center">60.1</td></tr><tr><td align="left">Unseen roles</td><td align="center">71.6</td><td align="center">63.6</td><td align="center">67.4</td><td align="center">39.2</td></tr><tr><td colspan="5"><hr/></td></tr><tr><td align="left">Seen AGENT roles</td><td align="center">100.0</td><td align="center">100.0</td><td align="center">100.0</td><td align="center">33.3</td></tr><tr><td align="left">Unseen AGENT roles</td><td align="center">100.0</td><td align="center">0.0</td><td align="center">0.0</td><td align="center">66.7</td></tr><tr><td colspan="5"><hr/></td></tr><tr><td align="left">Seen PATIENT roles</td><td align="center">100.0</td><td align="center">86.7</td><td align="center">92.9</td><td align="center">37.7</td></tr><tr><td align="left">Unseen PATIENT roles</td><td align="center">78.3</td><td align="center">66.9</td><td align="center">72.2</td><td align="center">62.3</td></tr><tr><td colspan="5"><hr/></td></tr><tr><td align="left">Seen ORIGIN roles</td><td align="center">97.1</td><td align="center">84.6</td><td align="center">90.4</td><td align="center">86.7</td></tr><tr><td align="left">Unseen ORIGIN roles</td><td align="center">14.3</td><td align="center">16.7</td><td align="center">15.4</td><td align="center">13.3</td></tr><tr><td colspan="5"><hr/></td></tr><tr><td align="left">Seen DESTINATION roles</td><td align="center">96.5</td><td align="center">91.6</td><td align="center">94.0</td><td align="center">86.2</td></tr><tr><td align="left">Unseen DESTINATION roles</td><td align="center">57.1</td><td align="center">63.2</td><td align="center">60.0</td><td align="center">13.8</td></tr></tbody></table></table-wrap> <table-wrap position="float" id="T4"><label>Table 4</label><caption><p>Model performance by predicate type.</p></caption><table frame="hsides" rules="groups"><thead><tr><td/><td align="left">Feature Set</td><td align="center">Precision</td><td align="center">Recall</td><td align="center">F-measure</td><td align="center">% of Roles</td></tr></thead><tbody><tr><td align="left">Nominal predicates</td><td align="left">Phrase-Chunking</td><td align="center">78.8</td><td align="center">63.0</td><td align="center">70.7</td><td align="center">79.2</td></tr><tr><td align="left">Verbal predicates</td><td align="left">Phrase-Chunking</td><td align="center">64.3</td><td align="center">52.9</td><td align="center">58.1</td><td align="center">20.8</td></tr><tr><td align="left">Nominal predicates</td><td align="left">Protein-Transport</td><td align="center">86.2</td><td align="center">75.8</td><td align="center">80.6</td><td align="center">79.2</td></tr><tr><td align="left">Verbal predicates</td><td align="left">Protein-Transport</td><td align="center">88.5</td><td align="center">67.6</td><td align="center">76.7</td><td align="center">20.8</td></tr><tr><td colspan="6"><hr/></td></tr><tr><td align="left">Wall Street Journal predicates</td><td align="left">Phrase-Chunking</td><td align="center">74.0</td><td align="center">62.7</td><td align="center">67.9</td><td align="center">34.3</td></tr><tr><td align="left">GeneRIF-only predicates</td><td align="left">Phrase-Chunking</td><td align="center">77.3</td><td align="center">60.7</td><td align="center">68.0</td><td align="center">65.7</td></tr><tr><td align="left">Wall Street Journal predicates</td><td align="left">Protein-Transport</td><td align="center">87.0</td><td align="center">79.7</td><td align="center">83.2</td><td align="center">34.3</td></tr><tr><td align="left">GeneRIF-only predicates</td><td align="left">Protein-Transport</td><td align="center">86.3</td><td align="center">72.1</td><td align="center">78.6</td><td align="center">65.7</td></tr></tbody></table></table-wrap> <table-wrap position="float" id="T5"><label>Table 5</label><caption><p>Corpus statistics.</p></caption><table frame="hsides" rules="groups"><thead><tr><td/><td align="right">All</td><td align="right">Train</td><td align="right">Test</td></tr></thead><tbody><tr><td align="left">GeneRIFs</td><td align="right">837</td><td align="right">637</td><td align="right">200</td></tr><tr><td align="left">Words</td><td align="right">21620</td><td align="right">16446</td><td align="right">5174</td></tr><tr><td align="left">Unique words</td><td align="right">3841</td><td align="right">3249</td><td align="right">1459</td></tr><tr><td colspan="4"><hr/></td></tr><tr><td align="left">Predicates</td><td align="right">911</td><td align="right">693</td><td align="right">218</td></tr><tr><td align="left">Unique predicates</td><td align="right">86</td><td align="right">72</td><td align="right">44</td></tr><tr><td align="left">Unique predicate lemmas</td><td align="right">34</td><td align="right">28</td><td align="right">25</td></tr><tr><td colspan="4"><hr/></td></tr><tr><td align="left">Roles</td><td align="right">1544</td><td align="right">1159</td><td align="right">385</td></tr><tr><td align="left">AGENT roles</td><td align="right">17</td><td align="right">14</td><td align="right">3</td></tr><tr><td align="left">PATIENT roles</td><td align="right">822</td><td align="right">623</td><td align="right">199</td></tr><tr><td align="left">ORIGIN roles</td><td align="right">173</td><td align="right">128</td><td align="right">45</td></tr><tr><td align="left">DESTINATION roles</td><td align="right">532</td><td align="right">394</td><td align="right">138</td></tr></tbody></table></table-wrap> <table-wrap position="float" id="T6"><label>Table 6</label><caption><p>Newswire semantic role chunk labels.</p></caption><table frame="hsides" rules="groups"><tbody><tr><td align="left">Sales</td><td align="left">B_ARG0</td></tr><tr><td align="left">declined</td><td align="left">O</td></tr><tr><td align="left">10</td><td align="left">B_ARG2</td></tr><tr><td align="left">%</td><td align="left">I_ARG2</td></tr><tr><td align="left">to</td><td align="left">O</td></tr><tr><td align="left">$</td><td align="left">B_ARG4</td></tr><tr><td align="left">251.2</td><td align="left">I_ARG4</td></tr><tr><td align="left">million</td><td align="left">I_ARG4</td></tr><tr><td align="left">from</td><td align="left">O</td></tr><tr><td align="left">$</td><td align="left">B_ARG3</td></tr><tr><td align="left">278.7</td><td align="left">I_ARG3</td></tr><tr><td align="left">million</td><td align="left">I_ARG3</td></tr><tr><td align="left">.</td><td align="left">O</td></tr></tbody></table></table-wrap> <table-wrap position="float" id="T7"><label>Table 7</label><caption><p>GeneRIF semantic role chunk labels.</p></caption><table frame="hsides" rules="groups"><tbody><tr><td align="left">to </td><td align="left">TO</td><td align="left">O</td></tr><tr><td align="left">induce</td><td align="left">VB</td><td align="left">O</td></tr><tr><td align="left">the</td><td align="left">DT</td><td align="left">O</td></tr><tr><td align="left">nuclear</td><td align="left">JJ</td><td align="left">B_DESTINATION</td></tr><tr><td align="left">translocation</td><td align="left">NN</td><td align="left">O</td></tr><tr><td align="left">of</td><td align="left">IN</td><td align="left">O</td></tr><tr><td align="left">NF-kappaB</td><td align="left">NN</td><td align="left">B_PATIENT</td></tr><tr><td align="left">transcription </td><td align="left">NN</td><td align="left">I_PATIENT</td></tr><tr><td align="left">factor</td><td align="left">NN</td><td align="left">I_PATIENT</td></tr></tbody></table></table-wrap> <table-wrap position="float" id="T8"><label>Table 8</label><caption><p>Features for Example 13.</p></caption><table frame="hsides" rules="groups"><thead><tr><td align="left">Word</td><td align="left">Predicate</td><td align="left">POS</td><td align="left">Phrase</td><td align="left">Clause</td></tr></thead><tbody><tr><td align="left">by</td><td align="left">import</td><td align="left">IN</td><td align="left">B-PP</td><td align="left">*</td></tr><tr><td align="left">increasing</td><td align="left">import</td><td align="left">VBG</td><td align="left">B-VP</td><td align="left">(*</td></tr><tr><td align="left">RING-dependent </td><td align="left">import</td><td align="left">JJ</td><td align="left">B-NP</td><td align="left">*</td></tr><tr><td align="left">BRCA1</td><td align="left">import</td><td align="left">NNP</td><td align="left">I-NP</td><td align="left">*</td></tr><tr><td align="left">nuclear</td><td align="left">import</td><td align="left">JJ</td><td align="left">I-NP</td><td align="left">*</td></tr><tr><td align="left">import</td><td align="left">import</td><td align="left">NN</td><td align="left">I-NP</td><td align="left">*</td></tr><tr><td align="left">and</td><td align="left">import</td><td align="left">CC</td><td align="left">O</td><td align="left">*</td></tr><tr><td align="left">inhibiting</td><td align="left">import</td><td align="left">VBG</td><td align="left">B-VP</td><td align="left">*</td></tr><tr><td align="left">BRCA1</td><td align="left">import</td><td align="left">JJ</td><td align="left">B-NP</td><td align="left">*</td></tr><tr><td align="left">nuclear</td><td align="left">import</td><td align="left">JJ</td><td align="left">I-NP</td><td align="left">*</td></tr><tr><td align="left">export</td><td align="left">import</td><td align="left">NN</td><td align="left">I-NP</td><td align="left">*)</td></tr></tbody></table></table-wrap>
<disp-formula><mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" id="M1" name="1471-2105-9-277-i1" overflow="scroll"><mml:semantics><mml:mrow><mml:mtable><mml:mtr><mml:mtd><mml:mrow><mml:mi>P</mml:mi><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mrow><mml:mi>c</mml:mi><mml:mi>o</mml:mi><mml:mi>r</mml:mi><mml:mi>r</mml:mi><mml:mi>e</mml:mi><mml:mi>c</mml:mi><mml:mi>t</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mrow><mml:mi>p</mml:mi><mml:mi>r</mml:mi><mml:mi>e</mml:mi><mml:mi>d</mml:mi><mml:mi>i</mml:mi><mml:mi>c</mml:mi><mml:mi>t</mml:mi><mml:mi>e</mml:mi><mml:mi>d</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:mfrac></mml:mrow></mml:mtd></mml:mtr><mml:mtr><mml:mtd><mml:mrow><mml:mi>R</mml:mi><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mrow><mml:mi>c</mml:mi><mml:mi>o</mml:mi><mml:mi>r</mml:mi><mml:mi>r</mml:mi><mml:mi>e</mml:mi><mml:mi>c</mml:mi><mml:mi>t</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mrow><mml:mi>r</mml:mi><mml:mi>e</mml:mi><mml:mi>f</mml:mi><mml:mi>e</mml:mi><mml:mi>r</mml:mi><mml:mi>e</mml:mi><mml:mi>n</mml:mi><mml:mi>c</mml:mi><mml:mi>e</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:mfrac></mml:mrow></mml:mtd></mml:mtr><mml:mtr><mml:mtd><mml:mrow><mml:msub><mml:mi>F</mml:mi><mml:mn>1</mml:mn></mml:msub><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mn>2</mml:mn><mml:mo>∗</mml:mo><mml:mi>P</mml:mi><mml:mo>∗</mml:mo><mml:mi>R</mml:mi></mml:mrow><mml:mrow><mml:mi>P</mml:mi><mml:mo>+</mml:mo><mml:mi>R</mml:mi></mml:mrow></mml:mfrac></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:mrow></mml:semantics></mml:math></disp-formula>
<table-wrap-foot><p>This table shows precision, recall, F-measure and labeled accuracy statistics for semantic role labeling models trained on various feature sets. "ABNER" indicates the results when using the ABNER-identified proteins instead of the manually annotated ones.</p></table-wrap-foot> <table-wrap-foot><p>This table shows precision, recall, F-measure split up by the type of role being identified. The final column indicates the percent of the total roles each role type accounted for. Performance numbers were calculated from the output of the Protein-Transport model when using manually annotated protein boundaries.</p></table-wrap-foot> <table-wrap-foot><p>This table shows precision, recall, F-measure comparing role phrases which appeared in both the training and testing data ("seen" roles) to role phrases which appeared only in the testing data ("unseen" roles). Both overall results and results by role type are shown. The final column indicates the percent of the particular category of roles that were seen (or unseen). Performance numbers were calculated from the output of the Protein-Transport model when using manually annotated protein boundaries.</p></table-wrap-foot> <table-wrap-foot><p>This table shows precision, recall, F-measure split up by the predicate part of speech and domain. A predicate was considered to be in the Wall Street Journal domain if the word appeared anywhere in the Wall Street Journal section of the Penn TreeBank, and was considered a GeneRIF-only predicate otherwise. The second column indicates which model (which feature set) the performance numbers are for. The final column indicates the percent of roles accounted for by each part of speech and each predicate domain.</p></table-wrap-foot> <table-wrap-foot><p>This table shows some basic statistics for the semantic roles annotated over the GeneRIFs in the protein transport corpus.</p></table-wrap-foot> <table-wrap-foot><p>This table shows the semantic role chunk labels for the Wall Street Journal sentence <italic>Sales declined 10% to $251.2 million from $258.7 million</italic>.</p></table-wrap-foot> <table-wrap-foot><p>This table shows the semantic role chunk labels for the GeneRIF phrase <italic>to induce the nuclear translocation of NF-kappaB transcription factor</italic>. The table also includes Penn TreeBank style part of speech tags for each word, and identifies what a one-word feature window for the classification of the word <italic>transcription </italic>looks like.</p></table-wrap-foot> <table-wrap-foot><p>This table shows the basic word-level features that were used to characterize each word in Example 13.</p></table-wrap-foot>
<graphic xlink:href="1471-2105-9-277-1"/>
[{"surname": ["Filmore", "Wooters", "Baker"], "given-names": ["CJ", "C", "CF"], "article-title": ["Building a Large Lexical Databank Which Provides Deep Semantics"], "source": ["The Pacific Asian Conference on Language, Information and Computation"], "year": ["2001"]}, {"surname": ["Kingsbury", "Palmer"], "given-names": ["P", "M"], "article-title": ["From Treebank to PropBank"], "source": ["Language Resources and Evaluation"], "year": ["2002"]}, {"surname": ["Palmer", "Gildea", "Kingsbury"], "given-names": ["M", "D", "P"], "article-title": ["The proposition bank: An annotated corpus of semantic roles"], "source": ["Computational Linguistics"], "year": ["2005"], "volume": ["31"], "fpage": ["71"], "lpage": ["105"]}, {"surname": ["Surdeanu", "Harabagiu", "Williams", "Aarseth"], "given-names": ["M", "S", "J", "P"], "article-title": ["Using predicate-argument structures for information extraction"], "source": ["ACL 2003"], "year": ["2003"]}, {"surname": ["Xue", "Palmer"], "given-names": ["N", "M"], "article-title": ["Calibrating features for semantic role labeling"], "source": ["EMNLP-2004"], "year": ["2004"]}, {"surname": ["Pradhan", "Hacioglu", "Krugler", "Ward", "Martin", "Jurafsky"], "given-names": ["S", "K", "V", "W", "JH", "D"], "article-title": ["Support Vector Learning for Semantic Argument Classification"], "source": ["Machine Learning"], "year": ["2005"], "volume": ["60"], "fpage": ["11"], "lpage": ["39"]}, {"surname": ["Toutanova", "Haghighi", "Manning"], "given-names": ["K", "A", "CD"], "article-title": ["Joint learning improves semantic role labeling"], "source": ["ACL 2005"], "year": ["2005"]}, {"surname": ["Punyakanok", "Koomen", "Roth", "tau Yih"], "given-names": ["V", "P", "D", "W"], "article-title": ["Generalized Inference with Multiple Semantic Role Labeling Systems"], "source": ["CoNLL-2005 Shared Task"], "year": ["2005"]}, {"surname": ["Pradhan", "Ward", "Martin"], "given-names": ["S", "W", "JH"], "article-title": ["Towards Robust Semantic Role Labeling"], "source": ["Computational Linguistics"]}, {"surname": ["Butt"], "given-names": ["M"], "article-title": ["The Light Verb Jungle"], "source": ["Harvard Working Papers in Linguistics"], "year": ["2003"], "volume": ["9"], "fpage": ["1"], "lpage": ["49"]}, {"surname": ["Carreras", "M\u00e0rquez"], "given-names": ["X", "L"], "article-title": ["Introduction to the CoNLL-2005 Shared Task: Semantic Role Labeling"], "source": ["CoNLL-2005 Shared Task"], "year": ["2005"]}, {"surname": ["Pradhan", "Sun", "Ward", "Martin", "Jurafsky"], "given-names": ["S", "H", "W", "JH", "D"], "article-title": ["Parsing Arguments of Nominalizations in English and Chinese"], "source": ["The Human Language Technology Conference/North American chapter of the Association for Computational Linguistics annual meeting (HLT/NAACL-2004)"], "year": ["2004"]}, {"surname": ["Jiang", "Ng"], "given-names": ["ZP", "HT"], "article-title": ["Semantic role labeling of NomBank: A maximum entropy approach"], "source": ["Conference on Empirical Methods in Natural Language Processing (EMNLP)"], "year": ["2006"], "fpage": ["138"], "lpage": ["145"]}, {"surname": ["Meyers", "Reeves", "Macleod", "Szekely", "Zielinska", "Young", "Grishman"], "given-names": ["A", "R", "C", "R", "V", "B", "R"], "article-title": ["Annotating Noun Argument Structure for NomBank"], "source": ["Conference on Language Resources and Evaluation (LREC)"], "year": ["2004"]}, {"surname": ["Chou", "Tsai", "Su", "Ku", "Sung", "Hsu"], "given-names": ["W", "R", "Y", "W", "T", "W"], "article-title": ["A Semi-Automatic Method for Annotating a Biomedical Proposition Bank"], "source": ["Proceedings of the Workshops on Frontiers in Linguistically Annotated Corpora 2006"], "year": ["2006"], "fpage": ["5"], "lpage": ["12"]}, {"article-title": ["Entrez gene"]}, {"article-title": ["GeneRIF \u2013 Gene reference into function"]}, {"surname": ["Hersh", "Bhupatiraju"], "given-names": ["W", "RT"], "article-title": ["TREC genomics track overview"], "source": ["Proceedings of The Twelfth Text REtrieval Conference"], "year": ["2003"]}, {"surname": ["Bhalotia", "Nakov", "Schwartz", "Hearst"], "given-names": ["G", "PI", "AS", "MA"], "article-title": ["BioText Team Report for the TREC 2003 Genomics Track"], "source": ["Proceedings of the Twelfth Text REtrieval Conference"], "year": ["2003"], "fpage": ["612"], "lpage": ["621"]}, {"surname": ["Jelier", "M", "Fijk", "Weeber", "Mulligen", "Schijvenaars"], "given-names": ["BMS", "S", "Cvd", "M", "Ev", "B"], "article-title": ["Searching for GeneRIFs: concept-based query expansion and bayes classification"], "source": ["Proceedings of The Twelfth Text REtrieval Conference"], "year": ["2003"]}, {"surname": ["Dalbey", "Von Heijne"], "given-names": ["RE", "G"], "source": ["Protein Targetting, Transport, and Translocation"], "year": ["2001"], "publisher-name": ["Academic Press"]}, {"surname": ["Lu"], "given-names": ["Z"], "article-title": ["Text Mining on GeneRIFs"], "source": ["PhD thesis"], "year": ["2007"], "publisher-name": ["University of Colorado Health Sciences Center"]}, {"surname": ["McNaught", "Black", "Ananiadou S, McNaught J"], "given-names": ["J", "W"], "article-title": ["Information Extraction"], "source": ["Text Mining for Biology and Biomedicine"], "year": ["2006"], "publisher-name": ["Artech House Publishers"]}, {"surname": ["Harabagiu", "Bejan", "Morarescu"], "given-names": ["S", "CA", "P"], "article-title": ["Shallow Semantics for Relation Extraction"], "source": ["IJCAI-05"], "year": ["2005"]}, {"article-title": ["Senseval 3"]}, {"surname": ["Marcus", "Santorini", "Marcinkiewicz"], "given-names": ["MP", "B", "MA"], "article-title": ["Building a Large Annotated Corpus of English: The Penn Treebank"], "source": ["Computational Linguistics"], "year": ["1994"], "volume": ["19"], "fpage": ["313"], "lpage": ["330"]}, {"surname": ["Kudo", "Matsumoto"], "given-names": ["T", "Y"], "article-title": ["Chunking with Support Vector Machines"], "source": ["North American Chapter of the Association for Computational Linguistics"], "year": ["2001"]}, {"surname": ["Hacioglu", "Pradhan", "Ward", "Martin", "Jurafsky"], "given-names": ["K", "S", "W", "JH", "D"], "article-title": ["Semantic Role Labeling by Tagging Syntactic Chunks"], "source": ["CoNLL-2004 Shared Task"], "year": ["2004"]}, {"surname": ["Lu", "Bada", "Ogren", "Cohen", "Hunter"], "given-names": ["Z", "M", "P", "KB", "L"], "article-title": ["Improving Biomedical Corpus Annotation Guidelines"], "source": ["Proceedings of the Joint BioLINK and 9th Bio-Ontologies Meeting, Fortaleza, Brazil"], "year": ["2006"]}, {"surname": ["Denis", "Baldridge"], "given-names": ["P", "J"], "article-title": ["Joint determination of anaphoricity and coreference resolution using integer programming"], "source": ["HLT/NAACL"], "year": ["2007"]}, {"surname": ["Pradhan", "Ramshaw", "Weischedel", "MacBride", "Micciulla"], "given-names": ["SS", "L", "R", "J", "L"], "article-title": ["Unrestricted Coreference: Identifying Entities and Events in OntoNotes"], "source": ["International Conference on Semantic Computing (ICSC)"], "year": ["2007"], "fpage": ["446"], "lpage": ["453"]}, {"surname": ["Kehler", "Appelt", "Taylor", "Simma"], "given-names": ["A", "D", "L", "A"], "article-title": ["The (non) utility of predicate-argument frequencies for pronoun interpretation"], "source": ["HLT-NAACL"], "year": ["2004"], "volume": ["4"], "fpage": ["289"], "lpage": ["296"]}, {"surname": ["Pradhan", "Hacioglu", "Ward", "Martin", "Jurafsky"], "given-names": ["S", "K", "W", "JH", "D"], "article-title": ["Semantic Role Chunking Combining Complementary Syntactic Views"], "source": ["CoNLL-2005 Shared Task"], "year": ["2005"]}, {"surname": ["Ogren"], "given-names": ["P"], "article-title": ["Knowtator: a Protege plugin for annotated copus construction"], "source": ["HLT-NAACL 2006"], "year": ["2006"]}, {"surname": ["Hacioglu"], "given-names": ["K"], "article-title": ["A Lightweight Semantic Chunking Model Based on Tagging"], "source": ["HLT/NAACL-04"], "year": ["2004"]}, {"surname": ["Hacioglu", "Ward"], "given-names": ["K", "W"], "article-title": ["Target Word Detection and Semantic Role Chunking Using Support Vector Machines"], "source": ["HLT/NAACL-03"], "year": ["2003"]}, {"surname": ["Lease", "Charniak"], "given-names": ["M", "E"], "article-title": ["Parsing Biomedical Literature"], "source": ["International Joint Conference on Natural Language Processing (IJCNLP), of Lecture Notes in Computer Science, Springer-Verlag"], "year": ["2005"], "volume": ["3651"], "fpage": ["58"], "lpage": ["69"]}, {"article-title": ["University of Pennsylvania morphology table"]}, {"surname": ["Ratnaparkhi"], "given-names": ["A"], "article-title": ["A Maximum Entropy Part-Of-Speech Tagger"], "source": ["The Empirical Methods in Natural Language Processing Conference"], "year": ["1996"]}, {"article-title": ["Conference on computational natural language learning (CoNLL-2000)"]}, {"article-title": ["Conference on Computational Natural Language Learning (CoNLL-2001)"]}]
BMC Bioinformatics. 2008 Jun 11; 9:277