Answers.Body: <p><em>First of all, I am not very familiar with details of NLP and NLU systems and concepts, so I will provide an answer based on the slides entitled <a href="https://web.archive.org/web/20170830051346/https://projects.ict.usc.edu/nld/cs599s13/LectureNotes/cs599s13dialogue1-30-13.pdf" rel="nofollow noreferrer">Natural language understanding in dialogue systems</a> (2013) by <a href="http://djdsite.org/" rel="nofollow noreferrer">David DeVaul</a>, a researcher on the topic.</em></p>
  
  <p>A dialogue system is composed of different parts or modules. Here's a diagram of an example of a dialogue system.</p>
  
  <p><a href="https://i.sstatic.net/SEZg1.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/SEZg1.png" alt="enter image description here"></a></p>
  
  <p>Each of these modules can introduce <strong>errors</strong>, which are then propagated to the rest of the pipeline. Of course, this is the first clear issue of such a dialogue system. Other issues or challenges include </p>
  
  <ul>
  <li><p><strong>ambiguity</strong> of natural language (and there are different types of ambiguity, i.e. see slide number 5), </p></li>
  <li><p><strong>synonyms</strong> (i.e. the dialogue system needs to handle different words or expressions that mean the same thing), </p></li>
  <li><p><strong>context-sensitivity</strong> (i.e. the same words or expressions can mean different things in different contexts)</p></li>
  <li><p><strong>semantic representation</strong> (i.e. how to represent semantics)</p></li>
  <li><p><strong>spontaneous speech</strong> (i.e. how to handle stuff like "hm", pauses, etc.)</p></li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-03-14T17:54:46.653Z
Answers.LastActivityDate: 2020-03-14T17:54:46.653Z
Answers.UserDisplayName: nbro
Answers.Body: <p>Dialogue is a hard problem because it requires pretty advanced cognitive functions. Leaving aside all the lower levels of language analysis (phonology if dealing with speech, morphology and syntax), you quickly run into interpretation problems that require a lot of world knowledge.</p>
  
  <p>Simple question and answer is fine, and restricted domains are somewhat easier as well. As soon as you get into a normal conversation, you will refer back to things you said before, so an NLP system would have to recognise that and resolve the reference accordingly. Typically in a conversation you would use variations of reference terms: the first time you mention an object you might describe it fully, but subsequently you will use shorter terms to refer to it.</p>
  
  <p>There is also a structure to conversation. This is typically modelled as conversational moves, and usually moves will have corresponding response-moves. For example, a common sequence would be greeting - greeting. Then you might have question - response - feedback. This sounds fairly easy, but once you try to annotate a dialogue with such moves you will find that it is pretty hard. As far as I am aware, there is no 'grammar' equivalent of describing the structure of conversations.</p>
  
  <p>Often, pragmatic meaning is interfering with the 'surface' meaning of utterances. A statement can actually function as a question, or a question can be a command (or a statement). The pragmatics of utterances depend on the context and also the relationship between the interlocutors. If I talk to my manager, I will use language differently than when I talk to my children.</p>
  
  <p>Dialogue/conversations are hard to analyse. Because of that, descriptive frameworks are still fairly limited. You need to keep track of what has said before, as that can change the way an utterance has to be interpreted. Grammatical analysis is a fairly solved problem, and word sense disambiguation as well. But pragmatics and conversational structure are still on the bleeding edge of linguistic research; at least they were when I was still teaching Discourse Analysis at university a few years ago.</p>
  
  <p>For that reason, chatbots are generally not very good. Sometimes they can fool people into believing they are human speakers, but this is usually done through trickery ("smoke and mirrors") rather than competent handling of conversational structures. It's all in the little box in nbro's answer labelled "DM"...</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-03-14T19:10:02.510Z
Answers.LastActivityDate: 2020-03-14T19:10:02.510Z
Answers.UserDisplayName: Oliver Mason
Body: <p>I've just started learning natural language processing from <a href="https://www.youtube.com/watch?v=3Dt_yh1mf_U&amp;list=PLQiyVNMpDLKnZYBTUOlSI9mi9wAErFtFm" rel="nofollow noreferrer">Dan Jurafsky's videos lectures</a>. In that video, minute 4:56, he is stating that dialogue is a hard problem in natural language processing (NLP). Why?</p>
  
Tags: <machine-learning><natural-language-processing>
Title: Why is dialogue a hard problem in natural language processing?
UserDisplayName: DRV
ThreadText: # Why is dialogue a hard problem in natural language processing?
  
  (Asked by: username_0 on 2020-03-13)
  
  I've just started learning natural language processing from [Dan Jurafsky's videos lectures](https://www.youtube.com/watch?v=3Dt_yh1mf_U&list=PLQiyVNMpDLKnZYBTUOlSI9mi9wAErFtFm). In that video, minute 4:56, he is stating that dialogue is a hard problem in natural language processing (NLP). Why?
  
  **Tags:** machine-learning, natural-language-processing
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2020-03-14. Score: 4 | Accepted answer
  
  Dialogue is a hard problem because it requires pretty advanced cognitive functions. Leaving aside all the lower levels of language analysis (phonology if dealing with speech, morphology and syntax), you quickly run into interpretation problems that require a lot of world knowledge.
  
  Simple question and answer is fine, and restricted domains are somewhat easier as well. As soon as you get into a normal conversation, you will refer back to things you said before, so an NLP system would have to recognise that and resolve the reference accordingly. Typically in a conversation you would use variations of reference terms: the first time you mention an object you might describe it fully, but subsequently you will use shorter terms to refer to it.
  
  There is also a structure to conversation. This is typically modelled as conversational moves, and usually moves will have corresponding response-moves. For example, a common sequence would be greeting - greeting. Then you might have question - response - feedback. This sounds fairly easy, but once you try to annotate a dialogue with such moves you will find that it is pretty hard. As far as I am aware, there is no 'grammar' equivalent of describing the structure of conversations.
  
  Often, pragmatic meaning is interfering with the 'surface' meaning of utterances. A statement can actually function as a question, or a question can be a command (or a statement). The pragmatics of utterances depend on the context and also the relationship between the interlocutors. If I talk to my manager, I will use language differently than when I talk to my children.
  
  Dialogue/conversations are hard to analyse. Because of that, descriptive frameworks are still fairly limited. You need to keep track of what has said before, as that can change the way an utterance has to be interpreted. Grammatical analysis is a fairly solved problem, and word sense disambiguation as well. But pragmatics and conversational structure are still on the bleeding edge of linguistic research; at least they were when I was still teaching Discourse Analysis at university a few years ago.
  
  For that reason, chatbots are generally not very good. Sometimes they can fool people into believing they are human speakers, but this is usually done through trickery ("smoke and mirrors") rather than competent handling of conversational structures. It's all in the little box in username_1's answer labelled "DM"...
  
  
  ---
  
  ### Answer by username_1 on 2020-03-14. Score: 2
  
  *First of all, I am not very familiar with details of NLP and NLU systems and concepts, so I will provide an answer based on the slides entitled [Natural language understanding in dialogue systems](https://web.archive.org/web/20170830051346/https://projects.ict.usc.edu/nld/cs599s13/LectureNotes/cs599s13dialogue1-30-13.pdf) (2013) by [David DeVaul](http://djdsite.org/), a researcher on the topic.*
  
  A dialogue system is composed of different parts or modules. Here's a diagram of an example of a dialogue system.
  
  [![enter image description here](https://i.sstatic.net/SEZg1.png)](https://i.sstatic.net/SEZg1.png)
  
  Each of these modules can introduce **errors**, which are then propagated to the rest of the pipeline. Of course, this is the first clear issue of such a dialogue system. Other issues or challenges include
  
  * **ambiguity** of natural language (and there are different types of ambiguity, i.e. see slide number 5),
  * **synonyms** (i.e. the dialogue system needs to handle different words or expressions that mean the same thing),
  * **context-sensitivity** (i.e. the same words or expressions can mean different things in different contexts)
  * **semantic representation** (i.e. how to represent semantics)
  * **spontaneous speech** (i.e. how to handle stuff like "hm", pauses, etc.)
  
  
  ---
  
  