<?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>semanticvoid &#187; Natural Language Processing</title>
	<atom:link href="http://semanticvoid.com/blog/index.php/category/natural-language-processing/feed/" rel="self" type="application/rss+xml" />
	<link>http://semanticvoid.com/blog</link>
	<description>extracting the semantics from the void</description>
	<lastBuildDate>Thu, 22 Sep 2011 21:05:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>WYCIWYS</title>
		<link>http://semanticvoid.com/blog/2011/09/21/wyciwys/</link>
		<comments>http://semanticvoid.com/blog/2011/09/21/wyciwys/#comments</comments>
		<pubDate>Wed, 21 Sep 2011 21:12:39 +0000</pubDate>
		<dc:creator>Administrator</dc:creator>
				<category><![CDATA[Hacking]]></category>
		<category><![CDATA[Natural Language Processing]]></category>
		<category><![CDATA[Yahoo!]]></category>
		<category><![CDATA[flickr]]></category>
		<category><![CDATA[hackday]]></category>

		<guid isPermaLink="false">http://semanticvoid.com/blog/?p=659</guid>
		<description><![CDATA[Many a times I&#8217;ve stared at Explored Flickr Photos and tried grokking its artistic nuances. My lack of artistic sensibility, at times causes me to fail to understand the photography techniques or properties that the photographer used or intended to capture. But the Flickr community is brimming with experts who often chime in about what [...]]]></description>
			<content:encoded><![CDATA[<p>Many a times I&#8217;ve stared at Explored Flickr Photos and tried grokking its artistic nuances. My lack of artistic sensibility, at times causes me to fail to understand the photography techniques or properties that the photographer used or intended to capture. But the Flickr community is brimming with experts who often chime in about what they like/see in comments. My #nlproc hack (for the upcoming Yahoo! Winter Hackday) aims to solve this by <em>summarizing</em> this expert knowledge (wisdom of crowd) for a photograph.</p>
<p><em><strong>W</strong>hat <strong>Y</strong>ou <strong>C</strong>omment <strong>I</strong>s <strong>W</strong>hat <strong>Y</strong>ou <strong>S</strong>ee</em> (<strong>WYCIWYS</strong>) is a Flickr hack that harnesses the comments of photos to determine the attributes/properties of the photo that people are talking about. It also gives a sentiment score (+ve) for each attribute to help a user gauge what other users find most interesting about a photo. Following are some outputs for WSCIWYS (<strong>click to zoom</strong>):</p>
<p><a href="http://semanticvoid.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-21-at-1.51.43-PM.png"><img class="size-medium wp-image-661 alignnone" title="image 1" src="http://semanticvoid.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-21-at-1.51.43-PM-300x195.png" alt="click to zoom" width="300" height="195" /></a></p>
<div class="mceTemp">
<dl id="attachment_663" class="wp-caption alignnone" style="width: 310px;">
<dt class="wp-caption-dt"><a href="http://semanticvoid.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-21-at-1.56.05-PM.png"><img class="size-medium wp-image-663" title="image 2" src="http://semanticvoid.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-21-at-1.56.05-PM-300x162.png" alt="click to zoom" width="300" height="162" /></a><a href="http://semanticvoid.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-21-at-1.59.43-PM.png"><img class="alignnone size-medium wp-image-666" title="image 3" src="http://semanticvoid.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-21-at-1.59.43-PM-300x161.png" alt="click to zoom" width="300" height="161" /></a><a href="http://semanticvoid.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-21-at-2.01.07-PM.png"><img class="alignnone size-medium wp-image-668" title="image 4" src="http://semanticvoid.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-21-at-2.01.07-PM-300x189.png" alt="click to zoom" width="300" height="189" /></a><a href="http://semanticvoid.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-21-at-2.04.11-PM.png"><img class="alignnone size-medium wp-image-669" title="image 5" src="http://semanticvoid.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-21-at-2.04.11-PM-300x192.png" alt="click to zoom" width="300" height="192" /></a></dt>
</dl>
</div>
]]></content:encoded>
			<wfw:commentRss>http://semanticvoid.com/blog/2011/09/21/wyciwys/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>what the bleep!</title>
		<link>http://semanticvoid.com/blog/2011/03/04/what-the-bleep-2/</link>
		<comments>http://semanticvoid.com/blog/2011/03/04/what-the-bleep-2/#comments</comments>
		<pubDate>Fri, 04 Mar 2011 19:13:15 +0000</pubDate>
		<dc:creator>Anand Kishore</dc:creator>
				<category><![CDATA[Abuse]]></category>
		<category><![CDATA[Hacking]]></category>
		<category><![CDATA[Natural Language Processing]]></category>
		<category><![CDATA[Research]]></category>
		<category><![CDATA[Yahoo!]]></category>
		<category><![CDATA[hackday]]></category>
		<category><![CDATA[nlp]]></category>
		<category><![CDATA[profanity]]></category>

		<guid isPermaLink="false">http://semanticvoid.com/blog/2011/03/04/</guid>
		<description><![CDATA[Profanity is often prevalent in user generated content (like comments). Websites that do not want to display such profane comments/content currently employ masking as a solution to get rid of profanity. Masking replaces the profanity in the content with characters like ####. The masked content still though conveys the existence of profanity to the user. [...]]]></description>
			<content:encoded><![CDATA[<p>Profanity is often prevalent in user generated content (like comments). Websites that do not want to display such profane comments/content currently employ masking as a solution to get rid of profanity. Masking replaces the profanity in the content with characters like ####. The masked content still though conveys the existence of profanity to the user. Humans have built up a great language model to infer missing words. Try it yourself &#8211; it should be easy for you to guess a bunch of profanity words for the following sentence:</p>
<blockquote><p>What the ####!</p></blockquote>
<p>My hack (<strong>Bleep</strong>) for the Yahoo! Spring &#8217;11 Hackday is yet another natural language hack that tries to remove the profanity from a comment without altering the semantics of the content. In brief, removing the profanity word from the content makes the parse tree less probable. The algorithm tries to alter this improbable parse tree to find the best local parse tree.</p>
<p>Following are some corrections suggested by <strong>Bleep</strong>:</p>
<p><a href="http://semanticvoid.com/blog/wp-content/uploads/Screen-shot-2011-03-04-at-12.39.53-PM1.png"><img src="http://semanticvoid.com/blog/wp-content/uploads/Screen-shot-2011-03-04-at-12.39.53-PM1.png" alt="" title="1" width="503" height="106" class="aligncenter size-full wp-image-603" /></a><br />
<a href="http://semanticvoid.com/blog/wp-content/uploads/Screen-shot-2011-03-04-at-12.40.25-PM1.png"><img src="http://semanticvoid.com/blog/wp-content/uploads/Screen-shot-2011-03-04-at-12.40.25-PM1.png" alt="" title="2" width="378" height="111" class="aligncenter size-full wp-image-604" /></a><br />
<a href="http://semanticvoid.com/blog/wp-content/uploads/Screen-shot-2011-03-04-at-12.40.56-PM1.png"><img src="http://semanticvoid.com/blog/wp-content/uploads/Screen-shot-2011-03-04-at-12.40.56-PM1.png" alt="" title="3" width="390" height="117" class="aligncenter size-full wp-image-605" /></a><br />
<a href="http://semanticvoid.com/blog/wp-content/uploads/Screen-shot-2011-03-04-at-12.41.22-PM1.png"><img src="http://semanticvoid.com/blog/wp-content/uploads/Screen-shot-2011-03-04-at-12.41.22-PM1.png" alt="" title="4" width="613" height="122" class="aligncenter size-full wp-image-606" /></a><br />
<a href="http://semanticvoid.com/blog/wp-content/uploads/Screen-shot-2011-03-04-at-12.41.51-PM1.png"><img src="http://semanticvoid.com/blog/wp-content/uploads/Screen-shot-2011-03-04-at-12.41.51-PM1.png" alt="" title="5" width="397" height="121" class="aligncenter size-full wp-image-607" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://semanticvoid.com/blog/2011/03/04/what-the-bleep-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>stop words</title>
		<link>http://semanticvoid.com/blog/2010/08/24/stop-words/</link>
		<comments>http://semanticvoid.com/blog/2010/08/24/stop-words/#comments</comments>
		<pubDate>Wed, 25 Aug 2010 04:00:16 +0000</pubDate>
		<dc:creator>Anand Kishore</dc:creator>
				<category><![CDATA[Natural Language Processing]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[text]]></category>

		<guid isPermaLink="false">http://semanticvoid.com/blog/?p=447</guid>
		<description><![CDATA[In a recent implementation for a near duplicate detection task I relied on stop words as key features in extracting signatures from text. The results turned out to be good but that&#8217;s not what I&#8217;m focusing on here. This was quite contrary to the mindset in the IR/NLP domain we have been accustomed to, where [...]]]></description>
			<content:encoded><![CDATA[<p>In a recent implementation for a near duplicate detection task I relied on stop words as key features in extracting signatures from text. The results turned out to be good but that&#8217;s not what I&#8217;m focusing on here. This was quite contrary to the mindset in the IR/NLP domain we have been accustomed to, where these words are considered meaningless and need to be got rid of before building any model/index. These word on the other hand encode a plethora of information like tense, plurality, (un)certainty, subjectivity and more. They bind the semantics of a sentence together and give them context. Yet (atleast in the IR sense) we give them a negative connotation (<em>STOP/NN -0.140192 sentiment</em>). I would go a step ahead by saying that we should stop calling them *stop* words and instead accept the inability of some IR systems of making correct use of them. How about *glue* words for a change? Or maybe not.</p>
<p>PS: Incase you are looking for a list of stop words for different languages here is a good list &#8211;  <a href=" http://members.unine.ch/jacques.savoy/clef/">http://members.unine.ch/jacques.savoy/clef/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://semanticvoid.com/blog/2010/08/24/stop-words/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Reading Less Is Reading More</title>
		<link>http://semanticvoid.com/blog/2009/10/07/reading-less-is-reading-more/</link>
		<comments>http://semanticvoid.com/blog/2009/10/07/reading-less-is-reading-more/#comments</comments>
		<pubDate>Wed, 07 Oct 2009 08:19:27 +0000</pubDate>
		<dc:creator>Anand Kishore</dc:creator>
				<category><![CDATA[Natural Language Processing]]></category>
		<category><![CDATA[Project]]></category>
		<category><![CDATA[dygest]]></category>

		<guid isPermaLink="false">http://semanticvoid.com/blog/?p=363</guid>
		<description><![CDATA[If information is what drives you to the internet, like me, you might be spending roughly 60-70% of your time online reading blogs, news and feeds (not to forget twitter). For me at least, reading online has superseded email (and updating social networks) as the most time consuming activity. And yet everyone is busy generating [...]]]></description>
			<content:encoded><![CDATA[<p>If information is what drives you to the internet, like me, you might be spending roughly 60-70% of your time online reading blogs, news and feeds (not to forget twitter). For me at least, reading online has superseded email (and updating social networks) as the most time consuming activity. And yet everyone is busy generating more content rather than finding a solution to consume all this information. We are trying to tackle this problem precisely with <a href="http://dyge.st">Dygest</a>. At its core <a href="http://dyge.st">Dygest</a> is a summarization engine that tries to sift through all the noise and present only the *real* content/news contained in any (news) article/text. Recently, we released an experimental version of a feed summarizer that uses the <a href="http://dyge.st">Dygest</a> engine to summarize blogposts/news for any RSS/ATOM feed. This summarized feed can be subscribed in any feed reader like Bloglines, Google Reader etc.</p>
<p><strong>NOTE</strong>: A feed that has not been encountered by our system ever before should be summarized in a couple of minutes.</p>
<p><center><img src="http://farm4.static.flickr.com/3423/3988948493_63da2cb1bd_o.png" alt="Feed Summarizer" /></center></p>
<p>On the whole with Dygest, reading blogs has now become much faster, much more concise and consuming information has become a great deal easier. Imagine the time saved reading the summarized version as compared to the original post (also you are not overwhelmed with useless information). See for yourself below:</p>
<p><center><img src="http://farm3.static.flickr.com/2594/3989711414_1f28fd59bd.jpg" alt="Original Post"/></p>
<p><strong>Original Post</strong></center></p>
<p>
<center><img src="http://farm3.static.flickr.com/2600/3988953559_d203feb1b6.jpg" alt="Summarized Post"/></p>
<p><strong>Summarized Post</strong></center></p>
<p>While you might have the urge to head over to Dygest and summarize your entire subscription list on Google Reader, I would recommend reading this post a bit further for some real cool stuff we have in store. If you must though &#8211; <a href="http://dyge.st">click here to Dygest</a>.</p>
<p><strong><br />
<h3>Summarizing Your Twitter Links</h3>
<p></strong></p>
<p><a href="http://readtwit.com">Readtwit</a> is a really cool service launched recently, which extracts links from your twitter feed and packages them in a clean RSS format. The awesome combination of Readtwit along with Dygest yields a summarized twitter feed delivered to your favorite feed reader.</p>
<p>Steps to get a summarized twitter feed:</p>
<p>(1) Sign into <a href="http://readtwit.com">Readtwit</a>.<br />
(2) Copy the link on the &#8216;Get me the feed&#8217; button:<br />
<center><img src="http://farm3.static.flickr.com/2454/3989734546_db979a08f5_m.jpg"/></center><br />
(3) Paste this link into the <a href="http://dyge.st">Dygest</a> interface and subscribe to the summarized feed returned in your favorite feed reader.<br />
<center><img src="http://farm3.static.flickr.com/2473/3988983827_57010939ff_o.png"/></center></p>
<p><strong><br />
<h3>More To Come</h3>
<p></strong></p>
<p>This is just an experimental release of <a href="http://dyge.st">Dygest</a> and so do send in your feedback on the summaries and help us improve. In the coming months we are working on improving the algorithms and churning out other great applications of <a href="http://dyge.st">Dygest</a> (there is something really cool in the works). So while we are busy teaching computers to read, <a href="http://dyge.st">Dygest</a> your feeds &#8211; because reading less is reading more.</p>
<p>Follow us on twitter &#8211; <a href="http://twitter.com/dygest">@dygest</a></p>
]]></content:encoded>
			<wfw:commentRss>http://semanticvoid.com/blog/2009/10/07/reading-less-is-reading-more/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>`Fact`orize Your Search</title>
		<link>http://semanticvoid.com/blog/2009/08/14/factorize-your-search/</link>
		<comments>http://semanticvoid.com/blog/2009/08/14/factorize-your-search/#comments</comments>
		<pubDate>Fri, 14 Aug 2009 07:37:08 +0000</pubDate>
		<dc:creator>Anand Kishore</dc:creator>
				<category><![CDATA[Hacking]]></category>
		<category><![CDATA[Natural Language Processing]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[Yahoo!]]></category>

		<guid isPermaLink="false">http://semanticvoid.com/blog/?p=308</guid>
		<description><![CDATA[Dygest and a hackday later, @sudheer_624 and I (@semanticvoid) are back with &#8216;dfacto&#8217;, codename for our latest search hack for Yahoo! Hackday Summer 2009. I think that search is undergoing a paradigm shift &#8211; its no longer about who presents the best ten blue links but now more about presenting the answers upfront. Dfacto (pronounced [...]]]></description>
			<content:encoded><![CDATA[<p><strong><a href="http://semanticvoid.com/blog/2009/03/19/dygest-your-search/">Dygest</a></strong> and a hackday later, <a href="http://twitter.com/sudheer_624">@sudheer_624</a> and I (<a href="http://twitter.com/semanticvoid">@semanticvoid</a>) are back with <strong>&#8216;dfacto&#8217;</strong>, codename for our latest search hack for Yahoo! Hackday Summer 2009.</p>
<p>I think that search is undergoing a paradigm shift &#8211; its no longer about who presents the best ten blue links but now more about presenting the answers upfront. <strong>Dfacto</strong> (pronounced as &#8216;<em>de facto</em>&#8216;, Latin for &#8216;<em>by [the] fact</em>&#8216;) is aimed at addressing this issue. A large percentage (nearly 68%) of queries are informational queries &#8211; one where the searcher knows what she&#8217;d like to do or find but does not know how this can be achieved. <strong>Dfacto</strong> is aimed primarily at addressing this class of queries by presenting a set of facts associated with the query/topic to the searcher. It uses natural language algorithms to get facts that are most &#8220;semantically&#8221; related to the query. In lay terms, it literally tries to understand your query and the results. I&#8217;ll save the algorithmic details for another post. The few examples below show how it works:</p>
<p><em>Disclaimer: This is a work in progress, so you might notice a few &#8216;facts&#8217; that are irrelevant to the query.</em></p>
<p>Lets say the searcher is (losing hair and) looking for causes of hair loss. Normally he/she would need to click through a bunch of links to get an overview on the causes. This hack on the other hand makes life a bit easier by presenting the causes upfront (click to enlarge):</p>
<p><center><a href="http://farm3.static.flickr.com/2525/3819295965_c7f9c3a651_o.png">click to enlarge<br /><img src="http://farm3.static.flickr.com/2525/3819295965_d8d3055f49.jpg" alt="'hair loss cause'" /></a><br /></center></p>
<p>Along with the facts, we also list the source from where it was extracted. Alternatively, the searcher can also select a bunch of facts he/she thinks are relevant and refine the search. This in turn would yield a new set of &#8216;web results&#8217; along with new refined and related &#8216;facts&#8217;.</p>
<p>Another example (one which I particularly like) is a query about &#8216;table manners&#8217;. This precisely lists a set of etiquette&#8217;s to follow at the table (click to enlarge).</p>
<p><center><a href="http://farm3.static.flickr.com/2587/3820121342_ac99f01072_o.png"> click to enlarge<br /> <img src="http://farm3.static.flickr.com/2587/3820121342_543ae9bb92.jpg" alt="'table manners'" /></a></center></p>
<p>Alternatively, <strong>Dfacto</strong> also serves well as a product research tool. A query for &#8216;iphone 3gs&#8217; yeilds (click to enlarge):</p>
<p><center><a href="http://farm3.static.flickr.com/2595/3820128618_cfbc2db7d6_o.png"> click to enlarge<br /> <img src="http://farm3.static.flickr.com/2595/3820128618_5fb29f2762.jpg" alt="'iphone 3gs'" /></a></center></p>
<p>On another note, if you have a date in the coming weeks you might be interested in reading the list below (:</p>
<p><center><a href="http://farm3.static.flickr.com/2669/3819328509_59c127b413_o.png"> click to enlarge<br /> <img src="http://farm3.static.flickr.com/2669/3819328509_ba08fe9e02.jpg" alt="'first date tips'" /></a></center></p>
<p>Happy hacking!</p>
]]></content:encoded>
			<wfw:commentRss>http://semanticvoid.com/blog/2009/08/14/factorize-your-search/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Dygest Your Search</title>
		<link>http://semanticvoid.com/blog/2009/03/19/dygest-your-search/</link>
		<comments>http://semanticvoid.com/blog/2009/03/19/dygest-your-search/#comments</comments>
		<pubDate>Fri, 20 Mar 2009 06:56:36 +0000</pubDate>
		<dc:creator>Anand Kishore</dc:creator>
				<category><![CDATA[Hacking]]></category>
		<category><![CDATA[Natural Language Processing]]></category>
		<category><![CDATA[Project]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[Yahoo!]]></category>
		<category><![CDATA[Add new tag]]></category>
		<category><![CDATA[summarization]]></category>

		<guid isPermaLink="false">http://semanticvoid.com/blog/?p=256</guid>
		<description><![CDATA[Update: This hack won the coveted &#8216;Search&#8217; category award. For the last couple of days, I and @sudheer_624 have been busy working on this hack for a Yahoo! Hackday. Although still a prototype, the hack has turned out to be interesting so we thought of putting it out for others to play around with. Dygest [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Update:</strong> This hack won the coveted &#8216;Search&#8217; category award.</p>
<p>For the last couple of days, I and <a href="http://twitter.com/sudheer_624">@sudheer_624</a> have been busy working on this hack for a Yahoo! Hackday. Although still a prototype, the hack has turned out to be interesting so we thought of putting it out for others to play around with.</p>
<p><strong>Dygest</strong> (pronounced as &#8216;digest&#8217; &#8211; thanks to <a href="http://twitter.com/bluesmoon">@bluesmoon</a>) is aimed at changing the conventional way of displaying search context via a snippet to a more informative, machine generated document summary. There two kinds of relevance for evaluating search results:</p>
<ul>
<li>Vertical relevance: determined by the ranking algorithms.</li>
<li>Horizontal relevance: the contextual information made available to the user about the result &#8211; Searchmonkey is a good initiative on this front.</li>
</ul>
<p>
The current way of displaying this context is via a snippet of text under every result. This snippet shows the neighborhood of the occurrence of the query terms. Usually this information is not rich enough for a searcher to make the right judgement about the result. This causes the searcher to switch back and forth between the documents and the search results if the the page is not relevant. This can be frustrating at times.</p>
<p>
<strong>Dygest</strong> aims to solve this by either replacing or enhancing the current search snippet with a summary of the result page. At its core lies a summarization engine which figures out what the *real* content of the page is (distinguishing it from the other junk like surrounding text, navigational text, comments etc) and then performs text summarization on this content. The summary of the page is then displayed to the user via the appropriate interface. How cool is that?</p>
<p>
The user no longer needs to click on irrelevant links. He/She can perceive the theme/important facts of the page from right within the results page. The other advantage of this is that it gives the user a good overview of the query topic &#8211; he no longer needs to spend time reading many long documents but rather read a few summaries from the top results to get a good overview of the subject. This is particularly well suited for mobile devices where its frustrating to switch back and forth between pages and the search results. This is also fit for news articles where we just need the important facts about the story. </p>
<p>
Well, here is an example to convince you. A search for &#8216;Carol Bartz&#8217; yields the following result which at the first glance is not at all informative.</p>
<p><center> <img alt="" border="2" src="http://farm4.static.flickr.com/3456/3369960208_48edc07644_o.png" title="search snippet for Carol Bartz" /> </center></p>
<p>
Enhancing the existing view with an abstract of the page helps gauge the content and theme of the document. This would now look like:</p>
<p><center> <img alt="" src="http://farm4.static.flickr.com/3637/3369975750_f0b313ae61_o.png" title="summarized view" /> </center></p>
<p><strong>Dygest</strong> outputs the following summaries for the query &#8216;<a href="http://datacracy.info/cgi-bin/dygest/search.py?q=iran+site%3Anews.yahoo.com">Iran</a>&#8216; restricted to Yahoo! News:</p>
<p><center><img alt="" src="http://farm4.static.flickr.com/3658/3370011200_a757dc42d8_o.png" title="Query for Iran" /></center></p>
<p>And following for &#8216;<a href="http://datacracy.info/cgi-bin/dygest/search.py?q=obama+stimulus+plan">Obama stimulus plan</a>&#8216;:</p>
<p><center><img alt="" src="http://farm4.static.flickr.com/3578/3370098322_1a73cd285b_o.png" title="obama stimulus plan"  /></center></p>
<p>Currently, <strong>Dygest</strong> has two interfaces &#8211; (1) a search interface powered by yahoo boss and (2) a searchmonkey plugin. Its just a prototype so be kind and don&#8217;t be too judgmental.</p>
<p>Start dygest<em>ing</em> <a href="http://datacracy.info/dygest/">here</a>.</p>
<p><center><br />
<script src="http://pipes.yahoo.com/js/imagebadge.js">{"pipe_id":"3hCWTB0Y3hG3E9xK6ycw5g","_btype":"image"}</script><br />
</center></p>
]]></content:encoded>
			<wfw:commentRss>http://semanticvoid.com/blog/2009/03/19/dygest-your-search/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>The Grammar Of Thought</title>
		<link>http://semanticvoid.com/blog/2008/09/03/the-grammar-of-thought/</link>
		<comments>http://semanticvoid.com/blog/2008/09/03/the-grammar-of-thought/#comments</comments>
		<pubDate>Wed, 03 Sep 2008 09:10:43 +0000</pubDate>
		<dc:creator>Anand Kishore</dc:creator>
				<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[Natural Language Processing]]></category>

		<guid isPermaLink="false">http://semanticvoid.com/blog/2008/09/03/the-grammar-of-thought/</guid>
		<description><![CDATA[Update: Found this interesting book related to this post &#8211; The Language Instinct [link] I have just started to scratch the surface of Natural Language Processing for my next project (involving NLP and Twitter &#8211; details to follow) and I already have a dozen questions bothering me. I shall attempt to put forth a few [...]]]></description>
			<content:encoded><![CDATA[<p><b> Update: </b> Found this interesting book related to this post &#8211; The Language Instinct [<a href="http://pinker.wjh.harvard.edu/books/tli/index.html">link</a>]</p>
<p>I have just started to scratch the surface of Natural Language Processing for my next project (involving NLP and Twitter &#8211; details to follow) and I already have a dozen questions bothering me. I shall attempt to put forth a few of the ideas and questions in this post. Lets talk briefly about the structure of language. Language has different levels of structure:</p>
<ol>
<li> dicourse &#8211; group of sentences</li>
<li> sentences</li>
<li> phrases</li>
<li> words</li>
<li> and so on&#8230;</li>
</ol>
<p>Between the &#8216;sentences&#8217; and &#8216;words&#8217; lies the syntactic structure of language. This syntactic structure is built using the <a href="http://en.wikipedia.org/wiki/Part-of-speech_tagging">parts of speech</a> of the words: nouns, verbs, etc. Words are grouped into phrases whose formation is governed by the grammar rules, for example:</p>
<p>Sentence -> &#8216;Noun Phrase&#8217; . &#8216;Verb Phrase&#8217;<br />
&#8216;Noun Phrase&#8217; -> Determiner . Adjective . Noun<br />
&#8216;Verb Phrase&#8217; -> Verb . &#8216;Noun Phrase&#8217;</p>
<p>A sentence is grammatically correct if it adheres to the grammar of the language (like described above). With just the above knowledge about language (something you might have learnt in the 5th grade) we can see that for a candidate sentence to make sense in some language, it has to be composed of meaningful components and these components have to be in some specific order for it to logically make sense.</p>
<p><b>Grammar of Thought</b></p>
<p>This has led me to ponder if an analogous grammar exists for &#8216;thought&#8217;. Our thoughts can also be broken down into meaningful components and the components here also have to follow some implicit ordering for the &#8216;thought&#8217; to make sense. If you think about the way you think, you will notice that as you run from one thought to another there is some logical connection between them just as between the sentences in a paragraph. If we could somehow get a formal representation of this grammar, wouldn&#8217;t it enable machines to think?</p>
<p><b>Language and Thought</b></p>
<p>There is enough literature out there which links the structure of language with the structure of thought. Benjamin Whorf states in his writings:</p>
<blockquote><p> the structure of a human being&#8217;s language influences the manner in which he understands reality and behaves with respect to it </p></blockquote>
<p>Thus, human cognition is based on the structure of language which in turn is the grammar defining the language. Hence a machine capable of generating sequence of grammatically correct sentences which also fit together logically (discourse), should have some ability of cognition. Even the Turing test uses natural language as a test for some level of cognition. Is this perspective of Natural Language Processing as a means of provisioning cognition to a machine, correct? Could this be another path for achieving artificial intelligence? I would love to get an answer to this from NLP experts out there.</p>
<p>Or is it just one of my other posts which don&#8217;t make sense because its 3am and I&#8217;m half asleep?</p>
]]></content:encoded>
			<wfw:commentRss>http://semanticvoid.com/blog/2008/09/03/the-grammar-of-thought/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.599 seconds -->

