<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Clog</title>
	<atom:link href="http://www.clres.com/blog/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://www.clres.com/blog</link>
	<description>CL Research Computational Lexicology Blog</description>
	<lastBuildDate>Fri, 23 Dec 2011 21:22:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Examining the Twitterverse with Content Analysis: A First Look</title>
		<link>http://www.clres.com/blog/?p=195</link>
		<comments>http://www.clres.com/blog/?p=195#comments</comments>
		<pubDate>Tue, 27 Sep 2011 20:38:26 +0000</pubDate>
		<dc:creator>Ken</dc:creator>
				<category><![CDATA[Content Analysis]]></category>
		<category><![CDATA[MCCA]]></category>
		<category><![CDATA[natural language processing]]></category>
		<category><![CDATA[tweets]]></category>
		<category><![CDATA[Twitterverse]]></category>

		<guid isPermaLink="false">http://www.clres.com/blog/?p=195</guid>
		<description><![CDATA[Analyzing Twitter data is becoming increasingly popular. Within the computational linguistics community, tweets are particularly challenging and interesting. The limitation of 140 characters would seem to make tasks easier, since sentences would be relatively short (e.g., compared to long sentences in newspaper articles). However, this limitation has brought with it some rather fundamental changes in [...]]]></description>
			<content:encoded><![CDATA[<p>Analyzing Twitter data is becoming increasingly popular. Within the computational linguistics community, tweets are particularly challenging and interesting. The limitation of 140 characters would seem to make tasks easier, since sentences would be relatively short (e.g., compared to long sentences in newspaper articles). However, this limitation has brought with it some rather fundamental changes in the way we communicate, primarily in the lexicon, with novel creations (e.g., &#8220;l8&#8243; for &#8220;late&#8221;). In addition, tweets are full of non-standard use of punctuation marks, particularly in creating emoticons, further complicating analysis. A recent paper by Kyle Dent and Sharoda Paul, &#8220;<a href="http://www.parc.com/publication/2745/through-the-twitter-glass.html" target="_blank">Through the Twitter Glass: Detecting Questions in Micro-text</a>&#8220;, took on the natural language processing (NLP) challenges (described briefly in a <a href="http://www.scientificamerican.com/article.cfm?id=parsing-the-twitterverse" target="_blank">Scientific American article</a>), developing NLP techniques to deal specifically with issues in tokenization, the lexicon, and parsing. They built a system to classify 2304 tweets into &#8220;real&#8221; questions and &#8220;not&#8221; questions (which had a superficial resemblance to questions). Tweets share a property with <a href="http://en.wikipedia.org/wiki/Likert_scale">Likert scales</a>, namely, that they are both short. The content analysis program MCCA (Minnesota Contextual Content Analysis) has been applied to an examination of Likert items in an attempt to improve the coherence of an entire scale. I modified MCCA slightly so that it would perform a classification task, applied it to the Twitter data used by Dent &amp; Paul, and achieved results almost as good, without having to deal with all the NLP issues. This would suggest that MCCA can provide an initial classification tool as a first step in the analysis of Twitter data. The MCCA analysis also showed that the tweets in this data set are extremely emotional, anti-practical, and anti-analytic.<span id="more-195"></span></p>
<p><a href="http://www.clres.com/mcca.html" target="_blank">MCCA</a> is a content analysis program designed to characterize texts based on the relative frequency with which words in categories are used, compared to norms determined from general usage statistics for the English language. It has been used in over 1500 studies since the early 1970s, primarily using a mainframe program at the University of Minnesota (with statistics on results used to determine any trends in general usage). The texts can range in size from short answers given to open-ended questions in questionnaires, newspaper articles, books, and multi-person transcripts such as focus groups or plays. MCCA takes about 4 seconds to analyze the 30,000 words in Hamlet. There are two primary sets of statistics used to characterize texts: (1) emphasis scores, showing the relative frequency of words in 116 categories (such as Feeling, Quantities, Spatial Sense, and Human Roles) and (2) context scores, profiling texts along four social context dimensions. The dimensions are traditional (judicial or religious texts), practical (newspaper articles, goal-oriented how-to texts), emotional (focus on personal involvement, such as leisure or recreation), and analytic (objective, research-oriented texts). The contextual analysis is a distinguishing characteristic of MCCA, determined from a principal components analysis of texts and each of which has a set of weights for each of the 116 emphasis categories. Typically, multiple texts are processed together to permit a comparison among them.</p>
<p>Underlying MCCA is a dictionary of 11,000 words, each of which has been assigned one or more categories (i.e., allowing ambiguity). As a text is processed, words with multiple categories are disambiguated using a running context score (so that the selected category is closest to the running context). The various statistics characterizing texts are essentially based on the words that can be categorized. Unknown words are relegated to a &#8220;leftover&#8221; category and generally do not participate in the analyses. Two principal statistics are distance matrices, one for emphasis scores and one for context scores, allowing an examination of the distances among the texts being analyzed (or the characters in a play).</p>
<p>As currently implemented, MCCA is not a classifier. However, it was straightforward to modify it so that it can be used as a classifier. To do this, a file containing multiple &#8220;texts&#8221; is processed to serve as the reference or marker set. (In the case of the Twitter data, the file was divided into two texts, one for instances deemed to be real questions and one for instances deemed not to be real questions. See the Dent &amp; Paul paper for a more complete description of these two sets.) Then, instances to be classified are processed one by one, with each instance first analyzed as an ordinary text, with emphasis and context scoring, and next compared to the reference texts, using the nearest distance as the criterion for the classification.</p>
<p>In this first look at the Twitter data, we simply put the two files (questions.txt and notquestions.txt) into one file, with separators to reflect the two sets. We then processed this file (in about 4 seconds). The size of this file is comparable to Hamlet (about 30,000 tokens), about 10 times as large as a smaller demonstration file of five texts. The first observation about the data is the percentage of words that could be categorized. For the demonstration file, about 90 percent of the words were classified; this is roughly what occurs for modern texts. For Hamlet, 83 percent are classified; this reflects the change in English over 400 years. For the Twitter data, only 77 percent of the words were classified; this is a clear indication that, with Twitter, a significant change in the language is occurring.</p>
<p>I next examined the various statistics generated by MCCA to attempt to discern any differences between the Questions and ¬Questions. There were non-zero distances between the two sets for both emphasis scores and context scores; it was not immediately clear whether these differences were important. One of the result sets is a difference analysis that shows the emphasis categories that are most different between the two sets. In this case, two categories looked most different: Move-in-Space (<em>forward, close, side</em>) and Who-Where (<em>who, which, someone, something</em>); these looked interesting.</p>
<p>The next step was to classify the instances. In this initial examination, I used the full Twitter data as the reference set and then classified each instance. I did not create a subset of the data to use as a &#8220;training set&#8221;, against which to classify the remaining instances as the &#8220;test set&#8221;. This would have been more rigorous, but I&#8217;m not sure that it would have been necessary in this first look. In this first test, I used the emphasis score distance as the criterion for classification. The results are shown in the following table:</p>
<table border="0" cellspacing="0" cellpadding="5" align="center">
<tbody>
<tr>
<td><strong>MCCA Results</strong></td>
<td style="text-align: center;"><strong>MT Questions</strong></td>
<td><strong>MT ¬Questions</strong></td>
</tr>
<tr>
<td><strong>MCCA Question</strong></td>
<td style="text-align: center;">708</td>
<td style="text-align: center;">433</td>
</tr>
<tr>
<td><strong>MCCA ¬Question</strong></td>
<td style="text-align: center;">444</td>
<td style="text-align: center;">717</td>
</tr>
</tbody>
</table>
<p>For comparison, the Dent-Paul results are shown the following table:</p>
<table border="0" cellspacing="0" cellpadding="5" align="center">
<tbody>
<tr>
<td><strong>Dent-Paul Results</strong></td>
<td style="text-align: center;"><strong>MT Questions</strong></td>
<td><strong>MT ¬Questions</strong></td>
</tr>
<tr>
<td><strong>Parser Question</strong></td>
<td style="text-align: center;">898</td>
<td style="text-align: center;">486</td>
</tr>
<tr>
<td><strong>Parser ¬Question</strong></td>
<td style="text-align: center;">254</td>
<td style="text-align: center;">666</td>
</tr>
</tbody>
</table>
<p>The MCCA results have a precision of 0.62050, a recall of 0.61458, and an accuracy of 0.61902. These compare with the Dent-Paul results, with a precision of 0.64484, a recall of 0.77951, and an accuracy of 0.67881.</p>
<p>My conclusion is that the MCCA results are quite comparable and were achieved with much less effort. I performed the same test using the context score distance, the five categories with the highest differences, and the single Who-Where category. In all these cases, the results were not as good, with only the top five categories achieving an accuracy of 0.61033, but with much lower precision. I&#8217;m not sure if any better results can be achieved with MCCA. It&#8217;s possible that use of various machine learning classifiers might optimize the results, but I don&#8217;t think this would be worth the effort on this data set, which may not be typical of Twitter data. I think this classification task is very difficult, particularly since the principal criterion for selecting tweets in the Dent &amp; Paul study was the presence of a question mark.</p>
<p>One very interesting aspect of the Twitter data is the overall contextual characterization of the two sets. As indicated above, the reference file was separated into two sets: Questions and ¬Questions. One of the statistics produced by MCCA is a table of the weighted context scores. Each context is normalized on a 50 point scale, from -25 to +25. The results in this case are shown in the following table:</p>
<table border="0" cellspacing="0" cellpadding="5" align="center">
<tbody>
<tr>
<td><strong>Text Group</strong></td>
<td style="text-align: center;"><strong>Traditional</strong></td>
<td style="text-align: center;"><strong>Practical</strong></td>
<td style="text-align: center;"><strong>Emotional</strong></td>
<td style="text-align: center;"><strong>Analytical</strong></td>
</tr>
<tr>
<td><strong>Average</strong></td>
<td style="text-align: center;">0.70</td>
<td style="text-align: center;">-10.35</td>
<td style="text-align: center;">24.30</td>
<td style="text-align: center;">-14.65</td>
</tr>
<tr>
<td><strong>Question</strong></td>
<td style="text-align: center;">1.04</td>
<td style="text-align: center;">-9.46</td>
<td style="text-align: center;">23.96</td>
<td style="text-align: center;">-15.54</td>
</tr>
<tr>
<td><strong>¬Question</strong></td>
<td style="text-align: center;">0.42</td>
<td style="text-align: center;">-11.07</td>
<td style="text-align: center;">23.96</td>
<td style="text-align: center;">-13.93</td>
</tr>
</tbody>
</table>
<p>In papers available through the MCCA link above, the point is made that in analyzing texts, the social context scores are almost never pure. Thus, these context scores are very surprising. They suggest that, at least for this set of Twitter data, the instances are almost purely emotional, with a strong anti-practical and anti-analytical bias, and a neutral score on traditional values. These results raise the question of whether this data is representative of the question universe and whether real questions that, for example, might be asked in a more practical and analytical context are being missed. Notwithstanding, the results make further examination of Twitter data in different contexts (e.g., in dealing with natural disasters or in situations like the Arab spring) would show different profiles. Clearly, this kind of analysis might prove to be very useful and interesting.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.clres.com/blog/?feed=rss2&#038;p=195</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Enhanced Word Sketches</title>
		<link>http://www.clres.com/blog/?p=179</link>
		<comments>http://www.clres.com/blog/?p=179#comments</comments>
		<pubDate>Thu, 10 Mar 2011 19:19:20 +0000</pubDate>
		<dc:creator>Ken</dc:creator>
				<category><![CDATA[Prepositions]]></category>
		<category><![CDATA[word-sense disambiguation]]></category>
		<category><![CDATA[word sketches]]></category>

		<guid isPermaLink="false">http://www.clres.com/blog/?p=179</guid>
		<description><![CDATA[Recently, I made a request on the ACL SIGLEX mailing list for tools that might help in analyzing preposition lexical samples. In this request, I indicated a need for software that would specifically provide enhanced word sketch analysis. I only received a couple of replies, one of which asked what I meant by this term. [...]]]></description>
			<content:encoded><![CDATA[<p>Recently, I made a <a href="http://www.clres.com/siglex/messdisp.php?id=140">request</a> on the ACL SIGLEX mailing list for tools that might help in analyzing preposition lexical samples. In this request, I indicated a need for software that would specifically provide <strong>enhanced word sketch analysis</strong>. I only received a couple of replies, one of which asked what I meant by this term. I responded, with some vagueness, but the interchange sparked some thoughts that are worth exploring further. In particular, this discussion raised questions about the amount of information in preposition dictionary entries and what might help in expanding these entries. I&#8217;d like to expand on this, particularly on the relation between current approaches to word-sense disambiguation (primarily statistical in nature) and what ends up in the dictionary. I think there is still something of a disconnect between the computational community and the lexicographers.</p>
<p><span id="more-179"></span></p>
<p><a href="http://trac.sketchengine.co.uk/attachment/wiki/SkE/DocsIndex/sketch-engine-elx04.pdf?format=raw">Adam Kilgarriff</a> developed the <a href="http://www.sketchengine.co.uk/">word sketch engine</a>, which has found great use among lexicographers. The main novelty of word sketches is the reliance on tagged corpora, in which each word receives a part of speech tag. Of particular note is that these tags constitute the terminals in a parse tree. However, the full parse tree showing constituents is not provided. Instead of a parse tree, some chunking of the terminals is performed, primarily using the <a href="http://www.fi.muni.cz/~thomas/corpora/CQL/">Corpus Query Language</a>. The sketches generate very useful information, including many syntactic relationships, through this bottom-up approach. To me, there are two major problems: (1) there is no constituent analysis and (2) there is no semantic analysis. Patrick Hanks has extended word sketches somewhat in what he&#8217;s doing with <a href="http://nlp.fi.muni.cz/projekty/cpa/">Corpus Pattern Analysis</a>. The focus of this analysis is on the identification of syntagmatic patterns (for verbs only). This pattern analysis has a strong affinity to FrameNet, but crucially adds some semantic characterization to the elements of the patterns using a shallow ontology. The development of these patterns is a labor-intensive effort, involving the development of patterns and the tagging of corpus instances with a pattern number until all instances (a sample if there is a large number) are completed. Currently, there is no automatic or semi-automatic tool to facilitate this process.</p>
<p>On the other side of the equation, the computational community has made substantial progress in identifying features useful in word-sense disambiguation (WSD). I&#8217;ll stick here to work in preposition WSD, since there is a smaller literature, but will sufficiently illustrate the process. The major contributions stem from the <a href="http://aclweb.org/anthology-new/S/S07/S07-1005.pdf">preposition disambiguation task</a> of SemEval-2007 and a comprehensive treatment by <a href="http://aclweb.org/anthology-new/J/J09/J09-2002.pdf">O&#8217;Hara &amp; Wiebe</a> (2009).  In SemEval-2007, there were three particpants: <a href="http://aclweb.org/anthology-new/S/S07/S07-1051.pdf">Ye &amp; Baldwin</a>, <a href="http://aclweb.org/anthology-new/S/S07/S07-1044.pdf">Yuret</a>, and <a href="http://aclweb.org/anthology-new/S/S07/S07-1040.pdf">Popescu et al</a>. <a href="http://aclweb.org/anthology-new/C/C10/C10-2052.pdf">Hovy et al.</a> built upon these results to make further advances in preposition disambiguation. While these efforts have identified and refined the set of features useful in preposition disambiguation, up to 85 percent accuracy, I don&#8217;t think they have fully explored the potential feature space.  To consider how enhanced word sketches might contribute further, we need to examine in detail what these features are and how they correspond to what&#8217;s in a dictionary.</p>
<p>Collocation features (the context) are the most important in preposition disambiguation. While the earlier studies focused on context windows, Hovy et al. found that the governor (the word to which a prepositional phrase is attached) and the object are of key importance, both of which are generally found within context windows, with the governor of greater importance than the object. Dictionaries do not generally provide any information about (the class of) the governor. One exception to this may be found in definitions of the preposition <strong>of</strong> (see the <a href="http://www.clres.com/cgi-bin/onlineTPP/find_prep.cgi">online preposition project data</a>), where several senses characterize the governor. Conversely, the definitions of many verbs and nouns will identify, explicitly or implicitly, an association with a specific preposition. For example, <strong>move</strong> (<em>go in a specified direction</em>) links well with a sense of <strong>to</strong> (<em>expressing motion in the direction of (a particular location)</em>); this is the kind of linkage (chain-clarifying relationship) investigated in Popescu et al. More preposition definitions characterize the preposition object, although some specify the semantic role of the object rather than properties of the object itself.</p>
<p>In the several studies, syntactic and semantic features are determined to be of less importance. However, a significant problem with this conclusion is the issue of how well available tools characterize these features. In these studies, semantic characterizations have examined only WordNet-based features. Since WordNet makes no claims about semantic classes, this conclusion must be held in abeyance.</p>
<p>The Preposition Project (TPP) has characterized many properties of each preposition sense. These have not been fully investigated in the several studies. TPP labels each sense according to its Quirk syntax; Hovy et al. used &#8220;fronting&#8221; (capitalization) as a feature; such a feature could be important for some prepositions but not for others. TPP identifies FrameNet frames and frame elements associated with each sense (based on the available corpus); these constitute an additional type of semantic characterization, possible relevant features that could be investigated. TPP also identifies other prepositions that can substitute; these were used by Yuret, who found that substitutions, while useful for disambiguation, did not work as well as for verbs and nouns. Potentially, these substitutions could be examined in conjunction with the <a href="http://www.clres.com/PrepositionClasses.htm">preposition classes</a> built from the TPP data; analysis of disambiguation properties by class has not yet been investigated. To some extent, coarse classes have been investigated through use of Penn Treebank (PTB) data; however, since prepositions were not accorded much prominence in PTB, further study may be warranted along these lines. O&#8217;Hara &amp; Wiebe and Hovy et al. both reported good results</p>
<p>In summary, what I&#8217;d like an enhanced word sketch to do is to enable me to tag (like a lexicographer), build syntagmatic patterns for each sense, and ultimately to be able to assign (I think) definitive frame elements to each sense. I&#8217;d want to put this into a dictionary in such a way that we could have something like a decision tree to identify the appropriate sense. I&#8217;m hoping that such a decision tree would greatly facilitate building an appropriate representation of which the PPs are placed in their proper subsidiary roles.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.clres.com/blog/?feed=rss2&#038;p=179</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Semantic Primitives</title>
		<link>http://www.clres.com/blog/?p=172</link>
		<comments>http://www.clres.com/blog/?p=172#comments</comments>
		<pubDate>Sat, 15 Jan 2011 22:30:12 +0000</pubDate>
		<dc:creator>Ken</dc:creator>
				<category><![CDATA[digraph analysis]]></category>
		<category><![CDATA[Electronic dictionaries]]></category>
		<category><![CDATA[Semantic Primitives]]></category>

		<guid isPermaLink="false">http://www.clres.com/blog/?p=172</guid>
		<description><![CDATA[In a recent posting to CORPORA on the topic of semantic primitives, John Sowa says, The so-called primitives are the result of analysis by adults who have learned how to write dissertations about language. I believe there are no primitives that are truly primitive in the sense that they cannot be analyzed in different ways [...]]]></description>
			<content:encoded><![CDATA[<p>In a <a href="http://mailman.uib.no/public/corpora/2011-January/012085.html">recent posting</a> to CORPORA on the topic of semantic primitives, John Sowa says,</p>
<blockquote><p>The so-called primitives are the result of analysis by adults who have  learned how to write dissertations about language. I believe there are  no primitives that are truly primitive in the sense that they cannot be  analyzed in different ways by different adults with different biases.</p></blockquote>
<p>While I won&#8217;t argue with John, I do believe such statements can have a discouraging effect on useful research. Throughout the 1970s and 1980s, research on machine-readable dictionaries (MRDs) was quite the rage. However, in 1991, Jean Veronis and Nancy Ide wrote a <a href="http://aclweb.org/anthology-new/E/E91/E91-1040.pdf">paper</a>, &#8220;An Assessment of Semantic Information Automatically Extracted from Machine Readable dictionaries.&#8221; They concluded that 55 to 70 percent of the data was garbled in some way. This paper had a similar discouraging effect on MRD research. I have been engaged in <a href="http://www.clres.com/online-papers/ell.doc">MRD research</a> for 40 years and would like to suggest that the search for primitives is not without value.</p>
<p><span id="more-172"></span>In general, I agree with John&#8217;s assessment of research on primitives. However, I think the one major reason for this is that such work tends to be very <em>a priori</em>, i.e., the result of people thinking about what should constitute a set of primitives. I agree that these various efforts are not very convincing. I have been critical of 1000 words of Basic English and the use of a defining vocabulary of 2000 words for the Longman&#8217;s dictionaries. I have been skeptical about Wierzbicka&#8217;s primitives and the WordNet tops because they were not derived from evidence. I am very skeptical about the root nodes in ontologies (all the rage these days).</p>
<p>In late 2001 and early 2002, I was fortunate to do some work for the <em>Oxford Dictionary of English</em> (ODE) in identifying what was called superordinates of noun definitions. At the time, Oxford had developed a noun hierarchy that was based in part on WordNet. I developed routines to parse these definitions and to generate these superordinates. I estimated that my work was about 85 percent correct and I was allowed to proceed. My exercise was a starting point for the Oxford lexicographers, who then following in behind me to correct my work and to use their expertise to fill in what I had not been able to accomplish. I believe the quality of this exercise is now visible in their new <a href="http://oxforddictionaries.com/">online dictionary</a> (which includes large sets of sentences from the Oxford English Corpus). This is certainly not the ultimate in identification of primitives, but it has the significant advantage that it is data-driven, i.e., <em>a posteriori</em>.</p>
<p>In addition to this exercise, I have made frequent use of digraph analysis of sets of definitions in an attempt to find primitives. I have done this for prepositions (<a href="http://www.clres.com/online-papers/PrepositionClasses.pdf">preposition classes</a> in the <a href="http://www.clres.com/cgi-bin/onlineTPP/find_prep.cgi">preposition project</a>), FrameNet&#8217;s <a href="http://www.clres.com/db/feindex.html">frame elements</a>, and 13,000 verbs in the Macquarie dictionary. Certainly not a be-all and end-all, but helpful in attempting to make sense of our wonderful language.</p>
<p>In some recent conversations on noun compounds with Robert Amsler (whose verb taxonomy derived from Merriam-Webster&#8217;s pocket dictionary set the tone for MRD research at the end of the 1970s), he has talked about how he views the potential of the latest <a href="http://ngrams.googlelabs.com/">Google corpus</a> for his efforts. Specifically,</p>
<blockquote><p>The simple rule that we accept in chemistry, that a compound may not  exhibit any of the properties of its component elements, doesn&#8217;t seem to  be understood as essentially true in the lexicon as well.</p></blockquote>
<p>I think the important point here is that, hopefully in some scientific manner, we can proceed to analyze these sorts of phenomena. I hope we don&#8217;t take John&#8217;s words to stifle such research.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.clres.com/blog/?feed=rss2&#038;p=172</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Semantic Analysis</title>
		<link>http://www.clres.com/blog/?p=159</link>
		<comments>http://www.clres.com/blog/?p=159#comments</comments>
		<pubDate>Sat, 04 Dec 2010 21:02:45 +0000</pubDate>
		<dc:creator>Ken</dc:creator>
				<category><![CDATA[Semantic Analysis]]></category>
		<category><![CDATA[inference steps]]></category>
		<category><![CDATA[representation of meaning]]></category>
		<category><![CDATA[word-sense disambiguation]]></category>

		<guid isPermaLink="false">http://www.clres.com/blog/?p=159</guid>
		<description><![CDATA[I recently developed an overview of the tasks in SemEval (the series of semantic evaluations conducted under the auspices of the ACL SIGLEX). The nice thing about this exercise was that it put semantic analysis into a larger perspective, where it becomes clearer where things are lacking. The overview groups the tasks into dictionary issues [...]]]></description>
			<content:encoded><![CDATA[<p>I recently developed an overview of the tasks in <a href="http://aclweb.org/aclwiki/index.php?title=SemEval_Portal">SemEval</a> (the series of semantic evaluations conducted under the auspices of the ACL SIGLEX). The nice thing about this exercise was that it put semantic analysis into a larger perspective, where it becomes clearer where things are lacking. The overview groups the tasks into dictionary issues and issues involving how sentence and textual elements fit together, the fruits of which are then available for application areas. After the first Senseval (the precursor to SemEval) was conducted, with a focus on word-sense disambiguation (WSD), the question was raised as to what purpose WSD served. The same question can be asked about all the other tasks. Attempting to answer this question may help to identify needed further tasks in SemEval, but also may help to identify how the various pieces of information may be used in different application areas. In what follows, I offer some opinions, particularly trying to identify other research that is relevant to the SemEval tasks.</p>
<p><span id="more-159"></span>In the area of dictionary issues, there are several holes. The main hole is that dictionary entries still do not contain the necessary information to enable disambiguation among multiple senses. Over the past 20 years, corpus linguistics has become the <em>sine qua non</em> among lexicographers. This has revolutionized the construction of dictionary entries, primarily due to the current reliance of corpus evidence, rather than made-up examples. With this use of corpus evidence, entries also increasingly attempt to characterize the <strong>constructions</strong> in which the entries appear (see <a href="http://books.google.com/books?id=Y2NgxCs7YbgC&amp;pg=PA205&amp;lpg=PA205&amp;dq=Atkins+and+Rundell&amp;source=bl&amp;ots=hWwgZFspfk&amp;sig=YuJmYeR61ezYri-41aYdRG1dvVY&amp;hl=en&amp;ei=l075TN-TJsGqlAeG4uifBw&amp;sa=X&amp;oi=book_result&amp;ct=result&amp;resnum=3&amp;ved=0CCAQ6AEwAg"><em>The Oxford Guide to Practical Lexicography</em></a>, Atkins &amp; Rundell, 2008). However, these characterizations seem only to contain syntactic information and little semantic information. There are some <strong>selectional restrictions</strong> or <strong>selectional preferences</strong>, but these are only minimal. The work of Patrick Hanks, in <a href="http://nlp.fi.muni.cz/projekty/cpa/">corpus pattern analysis</a>, attempts to rectify this shortcoming, and indicates how much work needs to be done in this area. Corpus evidence is also being used increasingly to characterize the collocational patterns of entries (see particularly <a href="http://www.webdante.com/">DANTE</a>). Now, in saying that this is insufficient to enable disambiguation, the proof of the pudding is that these characterizations do not yet fully incorporate the <strong>features</strong> that have been found useful in various WSD systems, particularly supervised systems, where investigators have tried a considerable panoply of textual attributes. The work of these researchers has not yet been incorporated into lexical databases. A second major hole in dictionaries is that entries do not contain a representation of the content of a sense that can be used to build a larger representation of a text. This hole leads into the second area in which SemEval tasks are focused.</p>
<p>Many SemEval tasks attempt to characterize how sentence and textual elements fit together, once some initial syntactic processing has been completed. In these tasks, an attempt is made to characterize chunks of text in a sentence and beyond (e.g., in &#8220;full texts&#8221;). These tasks include such things as semantic role labeling, semantic relation analysis, and coreference resolution. Now, what we&#8217;d really like here is a contribution from the lexicon, i.e., a representation that can be plugged into these analyses. There has been some beginning of this task with frame semantics, via the <a href="http://framenet.icsi.berkeley.edu/">FrameNet</a> project, where many lexical units trigger a frame consisting of frame elements, and where the frame definition and frame elements may be viewed as definitional in form. With its foray into full-text analysis, there is some beginning of intersentential relations. Another useful formalism is the lexicon development environment for use with unification-based linguistic formalisms, e.g, the <a href="http://wiki.delph-in.net/moin/FrontPage">LKB system</a>, which incorporates lexical items in HPSG systems.  <a href="http://www.sfu.ca/rst/">Rhetorical Structure Theory</a> provides another way of examining a text in its totality, but this theory has not been developed much of late. Importantly, as John Sowa points out in <a href="http://www.jfsowa.com/pubs/rolelog.pdf"><em>The Role of Logic and Ontology in Language and Reasoning</em></a>,</p>
<blockquote><p>Forty years of research in logic, linguistics, and AI has not produced a successful implementation: no computer system based on that approach can read one page of a high-school textbook and use the results to answer the questions and solve the problems as well as a B student.</p></blockquote>
<p>Semantic analysis plays a large role in what may be considered its ultimate application areas, such as information extraction, question answering, document summarization,  machine translation, paraphrasing, and recognizing textual entailment (RTE). The contributions of semantic analysis are difficult to assess in these tasks. Each has developed its own methods and there doesn&#8217;t seem to be any overarching analysis that identifies the specific contribution of semantic components. In many of these areas, investigators have begun to perform ablation analyses that seek to identify the relative contributions of its components. In RTE, the situation has become somewhat dire, where investigators do not have a clear idea of how results are being achieved. <a href="http://www.aclweb.org/anthology-new/P/P10/P10-1122.pdf">Sammons et al.</a> (2010), in &#8220;Ask Not What Textual Entailment Can Do for You&#8221;, have proposed a <a href="https://agora.cs.illinois.edu/display/rtedata/Explanation+Based+Analysis+of+RTE+Data">community-wide effort</a> to annotate RTE examples with  the inference steps required to reach a decision about the example. This indicates the scale of the effort.<em> </em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.clres.com/blog/?feed=rss2&#038;p=159</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Lexicologic Insights from Cognitive Neuroscience</title>
		<link>http://www.clres.com/blog/?p=132</link>
		<comments>http://www.clres.com/blog/?p=132#comments</comments>
		<pubDate>Sat, 20 Feb 2010 21:17:56 +0000</pubDate>
		<dc:creator>Ken</dc:creator>
				<category><![CDATA[Electronic dictionaries]]></category>
		<category><![CDATA[cognitive neuroscience]]></category>
		<category><![CDATA[computational lexicons]]></category>
		<category><![CDATA[meaning fragments]]></category>
		<category><![CDATA[ontologies]]></category>

		<guid isPermaLink="false">http://www.clres.com/blog/?p=132</guid>
		<description><![CDATA[The Number Sense: How the Mind Creates Mathematics (1999) and Reading in the Brain (2009), by Stanislas Dehaene, provide insights that can aid in the construction of computational lexicons. Dehaene describes how both reading and mathematics recruit structures of the brain that evolved for other purposes (the neuronal recycling hypothesis). There is a visual recognition [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://books.google.com/books?id=CbCDKLbm_-UC&amp;printsec=frontcover&amp;dq=Stanislas+Dehaene.+The+number+sense&amp;source=bl&amp;ots=KYKWS6pNR1&amp;sig=lTOxVRK1SukoQUY6PoEAE_KG_so&amp;hl=en&amp;ei=YelyS4SEKMeM8AaF0ZXJCw&amp;sa=X&amp;oi=book_result&amp;ct=result&amp;resnum=2&amp;ved=0CA8Q6AEwAQ#v=onepage&amp;q=&amp;f=false"><em>The Number Sense: How the Mind Creates Mathematics</em></a> (1999) and <a href="http://pagesperso-orange.fr/readinginthebrain/figures.htm"><em>Reading in the Brain</em></a> (2009), by <a href="http://en.wikipedia.org/wiki/Stanislas_Dehaene">Stanislas Dehaene</a>, provide insights that can aid in the construction of computational lexicons. Dehaene describes how both reading and mathematics recruit structures of the brain that evolved for other purposes (<strong>the neuronal recycling hypothesis</strong>). There is a visual recognition process that progressively extracts graphemes, syllables, prefixes, suffixes, word roots, and numbers. After this process, two routes in parallel activate speech creation and look-up in a mental lexicon. For both reading and mathematics, the processes are different from the computational processes implemented in computers (e.g., mathematical algorithms and parsing). Rather than attempting to optimize computational mechanisms for such processes, we can take a slightly different route by following the steps used by the brain to perform these tasks, i.e., accessing fragments of meaning in the mental lexicon.</p>
<p><span id="more-132"></span>Dehaene suggests that the number sense can be viewed as a sense just like the sense of smell or taste and can be found in many other animals besides humans. Although the number sense gave rise to mathematics, it is crucially different from the rigor and logic of mathematics; that is, the mind-computer metaphor does not hold up. If we look at how mathematics is performed, from a cognitive neuroscientific perspective, we can observe a combination of serial and parallel processing. This processing does not mirror the kind of processing used in looking up a word in an alphabetic dictionary and obtaining a definition. If we take this alternative route, we will not follow the logic of such things as ontologies, which have the same fatal flaws as the logical incompleteness of mathematics.</p>
<p>Dehaene describes the use of electroencephalograms (EEGs) to discern the order in which brain regions are activated. He particularly examines mathematical tasks, such as comparing two numbers to see which is larger. The main steps are planning, sequential ordering, decision making, and error correction; these steps are under the control of &#8220;executive areas&#8221; of the brain, which calls the necessary modules into play.</p>
<p>Dehaene&#8217;s methods provide the following general scenario: Some task is to be performed and different modules in the brain are activated in some order. Ten or twenty areas in the brain are activated in tasks such as reading words, examining their meaning, viewing a scene, or performing a calculation. Each region performs an elementary operation such as constructing a pronunciation or identifying the part of speech. The modules are generally very specific and very fine-grained. Our task is to identify and characterize the distinct fragments of meaning. Initially, we do not know exactly what fragments there are and we run the risk of imposing preconceptions into the process.</p>
<p>Dehaene suggests that reading first involves a &#8220;letterbox&#8221; which performs some recognition of a word (graphemes, syllables, prefixes, suffixes, word roots, and numbers). In examining the processing of strings, Dehaene identified a top-down sequence in assessing the meaning of a word. He used the strings EIGHTEEN, EINSTEIN, EXECUTE, and EKLPSGQI. Initially, visual areas are activated and then by a quarter-second, actual words were discriminated from meaningless words. At this point, activations differed for number words, proper nouns, or verbs and other words. There was a difference in response for major categories, i.e., access to the meaning of a word. In <em>The Number Sense</em>, Dehaene in 1997 summarizes these findings to indicate that the full characterization of all these nuances was only beginning; he noted that the number of questions could go on and on.</p>
<p>After presenting the details of observations, Dehaene goes on to consider the nature of mathematics in light of these discoveries. He concludes first that the brain-computer metaphor is not a good model of the data: the brain is not a logical machine. Dehaene goes on to examine axiomatic systems in mathematics (e.g., attempts by logicians such as Peano, Frege, and Russell to build a consistent basis for mathematics), leading up to Gödel&#8217;s Incompleteness Theorem. He concludes that mathematics has been subject to evolution, with increasing efficiency in its ability to express mathematical ideas. He suggests that this results from mathematical intuitions (e.g., Chinese words for numbers are much shorted to pronounce than English numbers, leading to greater efficiency in making simple calculations). The point of all this is that it is very easy to get hung up on and locked into mathematical formalisms, which may become problematic because of some ultimate inconsistency.</p>
<p>Mathematicians, particularly around the early 1900s, were very keen on building a logical structure for mathematics. Most notable was Bertrand Russell&#8217;s <em>Principia Mathematica</em>. These efforts were derailed by Gödel&#8217;s incompleteness theorems, which carried over to Turing machines and the advent of the digital computer. Lessons from these efforts should carry over to those who are attempting to develop ontologies. They will always be incomplete. In addition, the efforts to develop ontologies may obscure important aspects of our attempts to build dictionaries. They are focused too much on hierarchical representations (i.e., following the hypernymic backbone) and do not take into account all the many activations that may occur when we are confronted with bringing to bear knowledge about a word. (See the <a href="http://www.ontologyportal.org/">Suggested Upper Merged Ontology</a>, SUMO, the <a href="http://www.opencyc.org/">Cyc ontology</a>, <a href="http://wordnet.princeton.edu/">WordNet</a>, and the <a href="http://semanticweb.org/wiki/Main_Page">Semantic Web</a>.)</p>
<p>The problem is that there are too many pieces of information associated with a word: all the context that needs to be brought to bear (i.e., corpus linguistics), syntactic knowledge, semantic knowledge, relations with other parts of the lexicon, culture, etc. In the parser I use, the lexicon is designed for rapid access to syntactic information. It uses a hashing technique to access a word (i.e., it does not proceed by alphabetic lookup) and stores the word&#8217;s information in lists. These lists are nested, with syntactic categories at the first level and possibly other information as sublists providing limited amounts of context, subcategorization patterns, or various irregularities.</p>
<p>There is a growing field of computational neurolinguistics (see upcoming <a href="http://sites.google.com/site/compneurowsnaacl10/">workshop</a>), as well as attention being paid to optimal organization of the lexicon (another upcoming <a href="http://pageperso.lif.univ-mrs.fr/~michael.zock/cogalex-2.html">workshop</a>). At the moment, it seems that cognitive neuroscience is focused primarily on comparing models of the neural activity with various language resources. Important studies in this area include <a rel="nofollow" href="http://www.cs.cmu.edu/%7Etom/pubs/science2008.pdf">Mitchell et al. (2008)</a> and <a rel="nofollow" href="http://clic.cimec.unitn.it/brian/publications/murphyBaroniPoesio09eegRespondsConcepts.pdf">Murphy et al. (2009)</a>. The latter study particularly makes use of EEG data, but it was designed primarily to determine whether <em>a priori</em> semantic features were correlated with activation of particular brain regions. There are many fragments of meaning associated with individual words, so this kind of study is only a first step.</p>
<p>As I continue to investigate developments in these areas, I will be attempting to identify mechanisms that can be used in the design of computational lexicons. As an example of this, consider the first step of recognizing words, the hashing step I mentioned above. In my parser, the look-up phase computes a hash value for each word and accesses the location of its definition in the dictionary. The first step is to create an intermediate memory of all the parts of speech associated with the word, including the possibility that the string is merely a meaningless string and not a word at all. An important question is whether this is the most efficient access. It is this kind of question that will be informed by findings in cognitive neuroscience. I will draw upon these findings in later posts.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.clres.com/blog/?feed=rss2&#038;p=132</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Taxonomy Change Operations</title>
		<link>http://www.clres.com/blog/?p=126</link>
		<comments>http://www.clres.com/blog/?p=126#comments</comments>
		<pubDate>Fri, 29 Jan 2010 16:28:40 +0000</pubDate>
		<dc:creator>Ken</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[frame elements]]></category>
		<category><![CDATA[ontologies]]></category>
		<category><![CDATA[taxonomies]]></category>

		<guid isPermaLink="false">http://www.clres.com/blog/?p=126</guid>
		<description><![CDATA[I have been involved in the development of a frame element hierarchy or taxonomy, based on FrameNet&#8217;s frame-to-frame relations and frame element definitions. Since I know that this taxonomy is not perfect and can be improved, I need to consider the types of operations that might be involved in making changes. Although this may seem [...]]]></description>
			<content:encoded><![CDATA[<p>I have been involved in the development of a <a href="http://www.clres.com/db/feindex.html">frame element hierarchy or taxonomy</a>, based on FrameNet&#8217;s frame-to-frame relations and frame element definitions. Since I know that this taxonomy is not perfect and can be improved, I need to consider the types of operations that might be involved in making changes. Although this may seem a trivial task, a substantial amount of rigor needs to be maintained. Many other systems (particularly ontologies) also involve some sort of hierarchical relationships, principally the ISA relationship. The operations I consider will embrace these as well.</p>
<p><span id="more-126"></span>A taxonomy is a system of classification. (See the <a href="http://www.google.com/search?hl=en&amp;source=hp&amp;q=define%3A+taxonomy&amp;aq=f&amp;aql=&amp;aqi=l1g2&amp;oq=">definitions returned by Google</a>.) An ontology is very similar,  &#8220;<a href="http://wordnetweb.princeton.edu/perl/webwn?s=ontology">a rigorous and exhaustive organization of some knowledge domain that is usually hierarchical</a>&#8220;. A taxonomy contains a root, the top level node under which all the other concepts are organized. A taxonomy is a tree, with no cycles, so that when the full taxonomy is given, a strict hierarchy is produced, with the bottommost nodes called leaves.</p>
<p>Given a taxonomy, the following types of changes are envisioned:</p>
<ul>
<li><strong>adding a node</strong>: addition of a node may occur either as a new leaf or as an internal node</li>
<li><strong>deleting a node</strong>: removing a node from the taxonomy, again, either a leaf node or an internal node</li>
<li><strong>merging nodes</strong>: aggregating two or more nodes, possibly leading to the deletion of a node</li>
<li><strong>moving a subtree</strong>: changing the hypernym for a node, so that the node and all its children are moved in the taxonomy to another location</li>
<li><strong>splitting a node</strong>: creating subsets of the definitions of a given node, renaming the new subsets, and positioning the subsets at an appropriate place in the taxonomy</li>
</ul>
<p>In adding a node as a leaf, there is usually no difficulty as long as we retain the principles under which the taxonomy is being maintained. When we add an internal node, at some intermediate level of the taxonomy, we will need to consider whether we are adhering to these principles for what would be the children of the new internal node.  (For the frame element taxonomy, the addition of nodes will be performed when there is a change in FrameNet.)</p>
<p>Deleting a leaf node should also be straightforward, since we will not be affecting any other nodes in the taxonomy. Deleting an internal node, however, will have repercussions for its child nodes. A decision will have to be made on what to do with these, either deleting them as well or moving them to other places in the taxonomy. (For the frame element taxonomy, the deletion of nodes will be performed when there is a change in FrameNet.)</p>
<p>Merging nodes first involves assessing the target node, i.e., determining whether to keep the name or creating a new name. Second, we have to determine what happens to all the children of each of the nodes being merged. In creating the frame element taxonomy, nodes were merged when there was some problem with the  creation of the digraph image (e.g., a slash in the frame element name) or the node names were differed only in case. (For the frame element taxonomy, the merging of nodes will be performed when there is a compelling reason to do so; this reason will need to be stated explicitly.)</p>
<p>Moving a node, and possibly moving a subtree, involves changing the hypernym of the node. When doing so, it will be necessary to keep in mind the principles underlying the construction of the taxonomy and making sure that the children of the moved node will continue to adhere to these principles. (For the frame element taxonomy, the moving of nodes will be performed when there is a compelling reason to do so; this reason will need to be stated explicitly.)</p>
<p>Splitting a node is perhaps the most interesting operation in changing a taxonomy. First, it will be necessary to determine how to name the new nodes. Second, it will be necessary to identify how the children will be affected. In all likelihood, the children will be split into subsets, with some children going to each of the new nodes. (For the frame element taxonomy, the splitting of nodes will generally be based on an examination of the frame element definitions. It will generally be clear that a node being split has more than one sense. This operation is analogous to the splitting of a word&#8217;s meaning in a dictionary into subsenses.)</p>
<p>In making any changes to a taxonomy, it is important to keep a change log. In this way, the full explication of the taxonomy&#8217;s construction will be readily available for any further changes. (For the frame element taxonomy, a list of such changes may help the FrameNet lexicographer&#8217;s make modifications to the FrameNet data to ensure consistency.)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.clres.com/blog/?feed=rss2&#038;p=126</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Preposition Classes: General</title>
		<link>http://www.clres.com/blog/?p=120</link>
		<comments>http://www.clres.com/blog/?p=120#comments</comments>
		<pubDate>Thu, 21 Jan 2010 17:44:30 +0000</pubDate>
		<dc:creator>Ken</dc:creator>
				<category><![CDATA[digraph analysis]]></category>
		<category><![CDATA[Prepositions]]></category>
		<category><![CDATA[frame elements]]></category>
		<category><![CDATA[preposition classes]]></category>
		<category><![CDATA[semantic relations]]></category>

		<guid isPermaLink="false">http://www.clres.com/blog/?p=120</guid>
		<description><![CDATA[In The Preposition Project (TPP), each sense was assigned a semantic relation type by the lexicographer. These types were grouped together into 20 larger classes. The assignment of these two labels was a local decision, that is, without any a priori theoretical perspective. Once completed, the overall collection of these classifications are amenable to more [...]]]></description>
			<content:encoded><![CDATA[<p>In <a href="http://www.clres.com/cgi-bin/onlineTPP/find_prep.cgi">The Preposition Project</a> (TPP), each sense was assigned a semantic relation type by the lexicographer. These types were grouped together into 20 larger classes. The assignment of these two labels was a local decision, that is, without any <em>a priori</em> theoretical perspective. Once completed, the overall collection of these classifications are amenable to more detailed analysis. In particular, each class can be subjected to a digraph analysis and examined in relation to the other classes. In addition, the classes can be compared to the <a href="http://www.clres.com/db/fetax.php">frame element hierarchy</a>. The digraph analysis suggests that several of the classes are really subtypes of other classes. Examination of the frame element hierarchy assists in a clearer perception of the semantic roles filled by prepositional phrases.</p>
<p><span id="more-120"></span>The 20 classes of prepositions are: <strong>Activity</strong>, <strong>Agent</strong>, <strong>Backdrop</strong>, <strong>Barrier</strong>, <strong>Cause</strong>, <strong>Doubles</strong>, <strong>Exception</strong>, <strong>Means/Medium</strong>, <strong>Membership</strong>, <strong>Party</strong>, <strong>Possession</strong>, <strong>Quantity</strong>, <strong>Scalar</strong>, <strong>Spatial</strong>, <strong>Substance</strong>, <strong>Tandem</strong>, <strong>Target</strong>, <strong>Temporal</strong>, <strong>Topic</strong>, and <strong>Void</strong>. The 12 primitives in the frame element hierarchy are: <strong>Cause</strong>, <strong>State</strong>, <strong>Degree</strong>, <strong>Entity</strong>, <strong>Role</strong>, <strong>Purpose</strong>, <strong>Instrument</strong>, <strong>Phenomenon</strong>, <strong>Time</strong>, <strong>Path</strong>, <strong>Reason</strong>, and <strong>Topic</strong>. In the draft paper, <a href="http://www.clres.com/online-papers/PrepositionClasses.pdf"><em>Analysis of Preposition Classes</em></a>, I provide a detailed examination of each class, providing a link to the digraph for the class and identifying the FrameNet frames and frame elements evoked by the class.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.clres.com/blog/?feed=rss2&#038;p=120</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Preposition Disambiguation: State of the Art</title>
		<link>http://www.clres.com/blog/?p=103</link>
		<comments>http://www.clres.com/blog/?p=103#comments</comments>
		<pubDate>Fri, 30 Oct 2009 16:17:56 +0000</pubDate>
		<dc:creator>Ken</dc:creator>
				<category><![CDATA[Prepositions]]></category>
		<category><![CDATA[word-sense disambiguation]]></category>
		<category><![CDATA[collocational features]]></category>
		<category><![CDATA[semantic role features]]></category>
		<category><![CDATA[syntactic features]]></category>

		<guid isPermaLink="false">http://www.clres.com/blog/?p=103</guid>
		<description><![CDATA[Efforts to disambiguate prepositions have been increasing in the last few years, with claims of precision reaching 0.80. All such efforts present results in statistical generalities, with identification of the key factors related to the results. Continued progress in these efforts requires a close examination of limitations that have been noted. In addition, the exploitation [...]]]></description>
			<content:encoded><![CDATA[<p>Efforts to disambiguate prepositions have been increasing in the last few years, with claims of precision reaching 0.80. All such efforts present results in statistical generalities, with identification of the key factors related to the results. Continued progress in these efforts requires a close examination of limitations that have been noted. In addition, the exploitation of these results requires a close examination of the factors associated with each sense, so that the relevant information for each can be encoded in a meaningful way. This post summarizes the current literature on preposition disambiguation as a prelude to further developments of the data to be encoded in The Preposition Project (see sidebar link).</p>
<p><span id="more-103"></span></p>
<p>Meaningful preposition disambiguation requires a reasonably well-drawn sense inventory and a set of corpus instances that have been disambiguated by hand. <a href="http://www.clres.com/prepositions.html">The Preposition Project</a> (TPP) provides these. They were used in SemEval 2007 and have since been used in other studies; such studies constitute the basic set of references. Another important study, initiated prior to TPP, is <a style="opacity: 1;" href="http://aclweb.org/anthology-new/J/J09/J09-2002.pdf">O’Hara and Wiebe</a> (2009).</p>
<p>The basic SemEval task of disambiguating prepositions is described in <a href="http://acl.ldc.upenn.edu/W/W07/W07-2005.pdf">Litkowski &amp; Hargraves</a> (2007). There were three participants in this task, whose results are described in <a href="http://acl.ldc.upenn.edu/W/W07/W07-2051.pdf">Ye &amp; Baldwin</a> (2007), <a href="http://acl.ldc.upenn.edu/W/W07/W07-2044.pdf">Yuret</a> (2007), and <a href="http://acl.ldc.upenn.edu/W/W07/W07-2040.pdf">Popescu, Tonelli, &amp; Pianta</a> (2007). Two later studies have also used the SemEval datasets or TPP data: <a href="http://aclweb.org/anthology-new/N/N09/N09-3.pdf#page=106">Tratz &amp; Hovy</a> (2009) and <span><span><a href="http://140.116.245.248/ACL-IJCNLP-2009/EMNLP/pdf/EMNLP047.pdf">Dahlmeier, Ng,  and Schultz</a> (2009).</span></span></p>
<p><span><span>Each of these studies makes use of statistical techniques (decision trees, maximum entropy, likelihood, and chain-clarifying relationships) to identify significant features associated with preposition disambiguation. These features are not identical, in some part as a result of analyzing different pieces of information. One major difficulty is the lack of any consensus on what is used to classify noun and verb types.</span></span></p>
<p><span><span>Ye &amp; Baldwin used maximum entropy with three types of features: collocational features (open class words, WordNet synsets, named entities, surrounding words, and surrounding supersenses), syntactic features (parts of speech, chunk tags and types, and parse tree features), and semantic role features (semantic role tags, attached verbs, and verb relative positions). They found that collocational features played the most significant role. Tratz &amp; Hovy also used maximum entropy, but focused on syntactic structures for identifying words of interest. They found the verb/noun dominating the prepositional phrase, the noun/verb object of the preposition, the subject of the dominating verb, neighboring prepositional phrases, and words within 2 positions of the target. For each word so identified, they then constructed feature sets consisting of the word itself, the lemma, part of speech, synset members, hypernyms, and capitalization. They achieved an 8 percent improvement in disambiguation and concluded that words bearing some syntactic relation to the target preposition were responsible for the improvement.</span></span></p>
<p><span><span>Yuret examines the context of the target preposition using a statistical language model. His method is applied more generally to content words, where he looks at the general task of word-sense disambiguation using possible substitutes as a way of selecting an applicable sense. The method depends on a rich set of substitutes, which is not the case for prepositions. He makes the point that good quality substitutes for prepositions are unlikely, since they play a unique role in language. Notwithstanding, his results are sufficiently above the baseline and are supportive of the Ye &amp; Baldwin conclusions that collocational features are important. In addition, his results suggest that the TPP data for &#8220;other prepositions&#8221; associated with each sense might allow corpus instances for the different prepositions to be studied together.</span></span></p>
<p><span><span>Popescu et al. also examine the context of the preposition, but with the hypothesis that the collocational features constitute a mutual disambiguation process (chain-clarifying relationships). Their performance in SemEval was limited by the fact that the context words for the prepositions were not themselves disambiguated. Their method is based on a learning algorithm based on a supervised assignment of training instances (known as Angluin&#8217;s algorithm), but was limited to more superficial identification of the surrounding features.<br />
</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.clres.com/blog/?feed=rss2&#038;p=103</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Analyzing frame element definitions</title>
		<link>http://www.clres.com/blog/?p=86</link>
		<comments>http://www.clres.com/blog/?p=86#comments</comments>
		<pubDate>Mon, 28 Sep 2009 18:47:03 +0000</pubDate>
		<dc:creator>Ken</dc:creator>
				<category><![CDATA[digraph analysis]]></category>
		<category><![CDATA[frame elements]]></category>

		<guid isPermaLink="false">http://www.clres.com/blog/?p=86</guid>
		<description><![CDATA[As described in a previous post, a major step in laying out the frame element (FE) hierarchy involves an examination of the frame element definitions included in the characterizations of each frame in FrameNet. This step has now been completed, at least in a preliminary manner, with the result that the frame element hierarchy has [...]]]></description>
			<content:encoded><![CDATA[<p>As described in a <a href="http://www.clres.com/blog/?p=41">previous post</a>, a major step in laying out the frame element (FE) hierarchy involves an examination of the frame element definitions included in the characterizations of each frame in FrameNet. This step has now been completed, at least in a preliminary manner, with the result that the frame element hierarchy has been reduced to <a href="#prims">12 primitives</a> and the resulting digraph can now be viewed. The examination of frame element definitions has been both productive and instructive. This post describes how this analysis has proceeded.</p>
<p><span id="more-86"></span>As indicated earlier, frame elements with the same name may appear in many frames; the rigor of the FrameNet lexicographers in laying out a frame has resulted in a definition for each frame element. Thus, for example, there are 125 definitions of the <strong>Agent</strong> frame element. The FrameNet lexicographers are careful to point out that just because frame elements have the same name in different frames, the meaning of the frame element is not guaranteed to be the same. Nonetheless, as a working hypothesis, it is assumed that the meanings are the same. The practical effect of this hypothesis at the moment is that no detailed examination is made of the 125 definitions of the <strong>Agent</strong> frame element.</p>
<p>After applying initial steps in analyzing the frame element digraph, described in an <a href="http://www.clres.com/blog/?p=75">earlier post</a>, we had identified 261 primitives, consisting of 202 primitives not used as hypernyms and 59 used as hypernyms in deriving 750 frame elements. These frame elements are the ones whose definitions were examined. Frame element names are all nouns or noun phrases. In addition, many of the FE definitions use a typical noun hypernym that is present in the FE dictionary, e.g., <strong>Required</strong> is a <strong>State_of_Affairs</strong>. Since the FEs not used as hypernyms occur only infrequently in the frames, usually once or twice, these received the initial focus of my efforts. However, many FEs that are used as hypernyms (i.e., as identified in previous steps) also occur infrequently, these were also analyzed. The general goal of this analysis of FE definitions was <strong>to place the frame elements at an appropriate position in the frame element hierarchy</strong>.</p>
<p>To carry out this analysis, I created two files to keep track of the hypernym assignments I made, one for the unused FEs and one for the used FEs (both of these consisted of only the primitive FEs). These files contained, in tab-separated fields, the FE name, its frame, the FE type, and the FE definition. When I made an assignment, I copied all the elements from the initial files and put them in a pair of &#8220;assigned&#8221; files, adding the hypernym as another tab-separated field after the frame element type. I also modified the frame element dictionary to reflect the assignment. By changing the dictionary, I was able to immediately perform a new digraph analysis to determine the effect of my hypernym assignments, particularly to identify any circularities that may have arisen as a result and the progress I was making.</p>
<p>When I began examining the FE definitions, I found that I could make some assignments following previous steps, but where I had some doubts about making the assignment based only on the frame element name. When making hypernym assignments based on the FE definition, a general principle is to choose the most specific rather than the most general hypernym. This has the effect of spreading out the image, rather than having a large number of nodes directly adjacent to the primitive.</p>
<p>I made approximately 250 hypernym assignments based on the FE definitions. Many of these were quite straightforward, as in the following examples:</p>
<ul>
<li><strong>Route</strong>: &#8220;The Route is the usual path that the Vehicle travels&#8221; (Hypernym <strong>Path</strong>)</li>
<li><strong>Honoree</strong>: &#8220;The person for whom the Social_event is held&#8221; (Hypernym <strong>Person</strong>)</li>
<li><strong>Vividness</strong>: &#8220;The degree of detail and/or immediacy of a remembered Experience&#8221; (Hypernym <strong>Degree</strong>)</li>
<li><strong>Motivation</strong>: &#8220;The Reason for which an intentional act is performed&#8221; (Hypernym <strong>Reason</strong>)</li>
</ul>
<p>In making these assignments, the hypernym was immediately identified as being the name of another frame element in the dictionary, so there was little ambiguity in making the selection.</p>
<p>In examining the definitions, there eight frame elements that had no definitions. These frame elements came from frames that were themselves incomplete, i.e., they appeared to be frames in the process of development and not yet completely instantiated in FrameNet. Their deletion at this time does not appear to be problematic.</p>
<p>After about one-third of the FEs had been assigned hypernyms, the process became somewhat more difficult. Many FEs have definitions which are not really definitional, such as</p>
<ul>
<li><strong>Artist</strong>: &#8220;The Artist works off-stage to help make the Production&#8221;</li>
<li><strong>Accuracy</strong>: &#8220;This FE indicates the Accuracy of the prediction&#8221;</li>
<li><strong>Trigger</strong>: &#8220;The Trigger most commonly occurs in a PP Complement headed by _to_&#8221;</li>
<li><strong>Case</strong>: &#8220;The Case which a Trial is convened to decide&#8221;</li>
</ul>
<p>Clearly, these definitions are not useful in identifying an appropriate hypernym. To deal with such situations, I found that I could make use of an ordinary dictionary, where the noun frame element element names could be looked up and where their definitions would identify a noun hypernym. I chose to use an online version of the <em>Oxford Dictionary of English</em>, in which each noun definition is also placed into a noun hierarchy. I chose this dictionary rather than WordNet because its noun hierarchy was based on lexicographic principles, guided by the tops of the WordNet nouns.</p>
<p><a name="prims"></a>After making local decisions about each of the low-frequency frame elements, the digraph analysis resulted in the identification of 12 primitives: <strong>Cause</strong>, <strong>State</strong>, <strong>Degree</strong>, <strong>Entity</strong>, <strong>Role</strong>, <strong>Purpose</strong>, <strong>Instrument</strong>, <strong>Phenomenon</strong>, <strong>Time</strong>, <strong>Path</strong>, <strong>Reason</strong>, and <strong>Topic</strong>. These primitives look valid on their face. However, it needs to be noted that there are several hypernymic links, particularly those generated automatically based on the frame-to-frame relations, that need to be re-examined.</p>
<p>The frame element digraph consists of 1003 nodes, with the 12 primitive frame elements and 991 frame elements shown in a derivational path from the primitives. The <a href="http://www.clres.com/icons/FrameElements.jpg">resultant image</a> is quite large (4.0 MB) and may take some time to load in a browswer.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.clres.com/blog/?feed=rss2&#038;p=86</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>More circularities in the frame element hierarchy</title>
		<link>http://www.clres.com/blog/?p=83</link>
		<comments>http://www.clres.com/blog/?p=83#comments</comments>
		<pubDate>Mon, 28 Sep 2009 17:24:03 +0000</pubDate>
		<dc:creator>Ken</dc:creator>
				<category><![CDATA[digraph analysis]]></category>
		<category><![CDATA[frame-to-frame relations]]></category>
		<category><![CDATA[FrameNet]]></category>
		<category><![CDATA[strong components]]></category>

		<guid isPermaLink="false">http://www.clres.com/blog/?p=83</guid>
		<description><![CDATA[As suggested in another post, the assignment of hypernyms to frame elements may introduce additional circularities into the frame element hierarchy. This process is really quite elegant, and illustrates the value of the digraph analysis technique. First, the focus of making assignments is on frame elements that are viewed as primitives, i.e., without hypernyms and [...]]]></description>
			<content:encoded><![CDATA[<p>As suggested in another <a href="http://www.clres.com/blog/?p=60">post</a>, the assignment of hypernyms to frame elements may introduce additional circularities into the frame element hierarchy. This process is really quite elegant, and illustrates the value of the digraph analysis technique. First, the focus of making assignments is on frame elements that are viewed as primitives, i.e., without hypernyms and without any specific position in the hierarchy. Second, a decision to make a hypernym assignment is strictly local, made without consideration of placement into the hierarchy. Finally, rerunning the digraph analysis takes only a matter of seconds and immediately reveals the fact that an additional circularity has arisen, thus enabling a detailed analysis to break the circularity. This post chronicles the analysis of these additional circularities.</p>
<p><span id="more-83"></span></p>
<h4><strong>(</strong>Relation<strong>, </strong>Connection<strong>, </strong>Relationship<strong>)</strong></h4>
<p>This circularity arose when <strong>Relation</strong> was assigned the hypernym <strong>Connection</strong>, based on its definition as &#8220;The type of connection between the Individuals&#8221;. Links among these three frame elements are <strong>(</strong><strong>Relation</strong><strong> hyp </strong><strong>Connection</strong><strong>)</strong>, <strong>(</strong><strong>Connection</strong><strong> hyp Relationship</strong><strong>)</strong>, and <strong>(</strong><strong>Relationship</strong><strong> hyp </strong><strong>Relation</strong><strong>)</strong>. The second link was also created based on the frame element definition, specif., &#8220;Connection is the personal relationship between Individuals &#8230;&#8221;, while the third arose from the frame-to-frame relation <strong>Personal_relationship</strong> USES <strong>Relation_between_individuals</strong>. Each of these frame elements is used in only one frame and these terms may be viewed as essentially synonymous, but <strong>Relation</strong> seems to be the most general term. Both <strong>Relation</strong> and <strong>Relationship</strong> are defined as &#8220;the way in which <span>two or more people or things are connected&#8221;, suggesting that <strong>Relation</strong> should be given the hypernym <strong>Manner</strong>.</span></p>
<h4><strong>(Evaluee</strong><strong>, Victim</strong><strong>, Patient, Entity</strong><strong>)</strong></h4>
<p>This circularity arose when <strong>Patient</strong> was assigned the hypernym <strong>Entity</strong>, based on its definitions in 11 frames, mostly in some variation of &#8220;the entity that is being acted on&#8221;. The link from <strong>Entity</strong> to <strong>Evaluee</strong> comes from the frame-to-frame relation <strong>Aesthetics</strong> INHERITS <strong>Desirability</strong> and from <strong>Labeling</strong> USES <strong>Judgment_communication</strong>. The link from <strong>Evaluee</strong> to <strong>Victim</strong> comes from the frame-to-frame relation <strong>Corporal_punishment</strong> INHERITS <strong>Cause_harm</strong>. Making <strong>Evaluee</strong> the more general frame element in <strong>Desirability</strong> and <strong>Judgment_communication</strong> seems to have been a slightly inappropriate assignment. To break the circularity, <strong>Evaluee</strong> was deleted as the hypernym of <strong>Entity</strong> (making <strong>Entity</strong> the more primitive frame element, where <strong>Evaluee</strong> will eventually inherit <strong>Entity</strong> via the links from <strong>Evaluee</strong> to <strong>Victim</strong> to <strong>Patient</strong> to <strong>Entity</strong>).</p>
<h4><strong>(Degree</strong><strong>, Amount_of_information</strong><strong>)</strong></h4>
<p>This circularity arose when <strong>Amount_of_information</strong> was given the hypernym <strong>Degree</strong>. It&#8217;s definition (&#8220;The amount of information exchanged when communication occurs&#8221;) was not informative, but the example (&#8220;He never really [<strong>Amount_of_information</strong> fully] COMMUNICATED his intentions&#8221;) suggests that the meaning of this frame element can be suitably characterized as <strong>Degree</strong>. The reverse link, <strong>Degree</strong> having the hypernym <strong>Amount_of_information</strong>, arose from the frame-to-frame relations <strong>Attempt_suasion</strong> USES <strong>Communication</strong>, <strong>Communication_noise </strong>INHERITS <strong>Communication</strong>, <strong>Suasion</strong> USES <strong>Communication</strong>, and <strong>Volubility</strong> USES <strong>Communication</strong>. In these cases, <strong>Communication</strong> is the more general frame, so the use of <strong>Amount_of_information</strong> as the frame element seems overly specific. To break this circularity, <strong>Amount_of_information</strong> was removed as the hypernym of <strong>Degree</strong>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.clres.com/blog/?feed=rss2&#038;p=83</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

