<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Natural Language Pipeline for Chatbots</title>
	<atom:link href="http://pavel.surmenok.com/2016/11/05/natural-language-pipeline-for-chatbots/feed/" rel="self" type="application/rss+xml" />
	<link>http://pavel.surmenok.com/2016/11/05/natural-language-pipeline-for-chatbots/</link>
	<description></description>
	<lastBuildDate>Sat, 13 Apr 2019 17:14:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: surmenok</title>
		<link>http://pavel.surmenok.com/2016/11/05/natural-language-pipeline-for-chatbots/#comment-154</link>
		<dc:creator>surmenok</dc:creator>
		<pubDate>Tue, 16 Jan 2018 03:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://pavel.surmenok.com/?p=222#comment-154</guid>
		<description><![CDATA[Another idea. Entity recognition can be done by assigning a tag to each word (e.g. https://en.wikipedia.org/wiki/Inside%E2%80%93outside%E2%80%93beginning_(tagging) )
If you perform this kind of entity tagging first, then you can just a sequence of pairs (word, tag) into classification model instead of a sequence of words.
This way you don&#039;t increase complexity of the model too much.]]></description>
		<content:encoded><![CDATA[<p>Another idea. Entity recognition can be done by assigning a tag to each word (e.g. <a href="https://en.wikipedia.org/wiki/Inside%E2%80%93outside%E2%80%93beginning_(tagging)" rel="nofollow">https://en.wikipedia.org/wiki/Inside%E2%80%93outside%E2%80%93beginning_(tagging)</a> )<br />
If you perform this kind of entity tagging first, then you can just a sequence of pairs (word, tag) into classification model instead of a sequence of words.<br />
This way you don&#8217;t increase complexity of the model too much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kaushik Govindarajan</title>
		<link>http://pavel.surmenok.com/2016/11/05/natural-language-pipeline-for-chatbots/#comment-153</link>
		<dc:creator>Kaushik Govindarajan</dc:creator>
		<pubDate>Tue, 16 Jan 2018 02:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://pavel.surmenok.com/?p=222#comment-153</guid>
		<description><![CDATA[That sounds like good approach. So while converting my words to vectors I need to add additional features for the entities. While predicting, the NER has to be done first and based on its output I can predict the intent also. But the only thing that concerns me is that the features will keep increasing as my entities increase and hence the classification algorithm may not perform well.
Thanks]]></description>
		<content:encoded><![CDATA[<p>That sounds like good approach. So while converting my words to vectors I need to add additional features for the entities. While predicting, the NER has to be done first and based on its output I can predict the intent also. But the only thing that concerns me is that the features will keep increasing as my entities increase and hence the classification algorithm may not perform well.<br />
Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: surmenok</title>
		<link>http://pavel.surmenok.com/2016/11/05/natural-language-pipeline-for-chatbots/#comment-152</link>
		<dc:creator>surmenok</dc:creator>
		<pubDate>Sun, 14 Jan 2018 19:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://pavel.surmenok.com/?p=222#comment-152</guid>
		<description><![CDATA[Yes. One way to do this is to perform entity recognition first, and then add features like HasTime (0 or 1), HasDate (0 or 1).  Using such features together with raw text of the message can be very helpful.]]></description>
		<content:encoded><![CDATA[<p>Yes. One way to do this is to perform entity recognition first, and then add features like HasTime (0 or 1), HasDate (0 or 1).  Using such features together with raw text of the message can be very helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kaushik Govindarajan</title>
		<link>http://pavel.surmenok.com/2016/11/05/natural-language-pipeline-for-chatbots/#comment-151</link>
		<dc:creator>Kaushik Govindarajan</dc:creator>
		<pubDate>Sun, 14 Jan 2018 15:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://pavel.surmenok.com/?p=222#comment-151</guid>
		<description><![CDATA[Thanks, I am aware of the entity extraction part but I was wondering if there is a way to tell the classifier that a time expression is expected in this part of the sentence. This might significantly improve the performance of the classifier.]]></description>
		<content:encoded><![CDATA[<p>Thanks, I am aware of the entity extraction part but I was wondering if there is a way to tell the classifier that a time expression is expected in this part of the sentence. This might significantly improve the performance of the classifier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: surmenok</title>
		<link>http://pavel.surmenok.com/2016/11/05/natural-language-pipeline-for-chatbots/#comment-150</link>
		<dc:creator>surmenok</dc:creator>
		<pubDate>Sat, 13 Jan 2018 18:17:00 +0000</pubDate>
		<guid isPermaLink="false">http://pavel.surmenok.com/?p=222#comment-150</guid>
		<description><![CDATA[intent is restaurant_booking. &quot;7pm tomorrow&quot; is an entity, you should treat it as entity recognition problem. Parsing dates and times can be quite hard because there are many ways how people can express it. This article about x.ai architecture for natural language understanding may help: https://x.ai/blog/a-peek-at-x-ais-data-science-architecture/ They deal with datetime parsing a lot.]]></description>
		<content:encoded><![CDATA[<p>intent is restaurant_booking. &#8220;7pm tomorrow&#8221; is an entity, you should treat it as entity recognition problem. Parsing dates and times can be quite hard because there are many ways how people can express it. This article about x.ai architecture for natural language understanding may help: <a href="https://x.ai/blog/a-peek-at-x-ais-data-science-architecture/" rel="nofollow">https://x.ai/blog/a-peek-at-x-ais-data-science-architecture/</a> They deal with datetime parsing a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kaushik Govindarajan</title>
		<link>http://pavel.surmenok.com/2016/11/05/natural-language-pipeline-for-chatbots/#comment-149</link>
		<dc:creator>Kaushik Govindarajan</dc:creator>
		<pubDate>Sat, 13 Jan 2018 14:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://pavel.surmenok.com/?p=222#comment-149</guid>
		<description><![CDATA[Hi Pavel, the article serves as a good intro to a newbie. In response to the last part of your post, I am currently building an intent classifier and I have a brief idea about the training of static questions that contain hardcoded text. I am having problems in training sentences with temporal data. For ex. consider and example sentence and an intent 
Book a table for 2 at 7pm tomorrow - restaurant_booking 
Now in this case &quot;7pm tomorrow&quot; is an arbitrary value and a user can enter any time expression. So in this case how should I structure my training data in order to train a more accurate model?]]></description>
		<content:encoded><![CDATA[<p>Hi Pavel, the article serves as a good intro to a newbie. In response to the last part of your post, I am currently building an intent classifier and I have a brief idea about the training of static questions that contain hardcoded text. I am having problems in training sentences with temporal data. For ex. consider and example sentence and an intent<br />
Book a table for 2 at 7pm tomorrow &#8211; restaurant_booking<br />
Now in this case &#8220;7pm tomorrow&#8221; is an arbitrary value and a user can enter any time expression. So in this case how should I structure my training data in order to train a more accurate model?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
