<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">An Information Retrieval-based Approach for Building Intuitive Chatbots for Large Knowledge Bases</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Andreas</forename><surname>Lommatzsch</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">DAI-Labor</orgName>
								<orgName type="institution">TU Berlin</orgName>
								<address>
									<addrLine>Ernst-Reuter-Platz 7</addrLine>
									<postCode>D-10587</postCode>
									<settlement>Berlin</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Jonas</forename><surname>Katins</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">DAI-Labor</orgName>
								<orgName type="institution">TU Berlin</orgName>
								<address>
									<addrLine>Ernst-Reuter-Platz 7</addrLine>
									<postCode>D-10587</postCode>
									<settlement>Berlin</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">An Information Retrieval-based Approach for Building Intuitive Chatbots for Large Knowledge Bases</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">A81073BC4F14AF0174A4ACEFD4DD45D4</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T18:28+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>chatbots</term>
					<term>information retrieval</term>
					<term>context</term>
					<term>human-computer interaction</term>
					<term>natural language processing</term>
					<term>question answering</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Finding quickly the relevant information is essential in many application scenarios. In the past years, huge data collections have been created, but for most users it is still very difficult to find the information relevant for a specific, often complex problem. With the advances in automatic language processing chatbots have been developed to simplify the information search providing an intuitive user interface that gives the user the needed information in a natural dialog. In this work we present a chatbot framework that answers questions related to services offered by the public administration. The framework enables complex dialogs and supports the user with giving hints and recommendations. Based on the framework, public chatbot services have been deployed for two major German cities designed to answer questions related to offered service, locations, and appointments. The paper discusses the architecture of the system and explains the developed algorithms. We report experiences running the systems as well as discuss the strengths and weaknesses of the developed approach.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>Personal assistants are getting more and more popular in a growing number of domains. These "virtual agents" act as experts providing answers to questions and supporting users in solving routine tasks. These personal bots have been developed as an additional channel to FAQs, hotlines and forums enabling a natural interactive conversation with the user. In contrast to classic search systems, chatbots should support longer dialogs (interactive search) and guide the user in finding information for complex problems. In addition, chatbots should be able to handle both keyword queries and complex "natural" sentences.</p><p>The development of chatbots leads to several challenges. One main problem is the variety of ways that can be used for describing a problem. In addition, the used vocabulary and the meaning of terms often depend on a specific domain.</p><p>This typically requires large collections of training data from the target domain. For very narrow scenarios (e.g., ordering a pizza) the training data might be created within an acceptable timeframe; for more general scenarios characterized by several thousand information objects, the generation of training data is extremely expensive and often infeasible at all. Thus, the use of information retrieval approaches extracting queries from natural user inputs seems to be a promising approach.</p><p>Another challenge is the translation of colloquial language into the often formal "official" language used in knowledge bases created by domain experts. Moreover, users do not pay much attention to spelling and correct grammar in chat interfaces. Thus, natural language analysis tools typically trained on large text corpora show only a limited precision.</p><p>In this work we present our approach for building a chatbot framework optimized for answering questions related to the services offered by public administration (e.g., applying for a new passport or registering an apartment). The framework combines Information Retrieval techniques and machine learning methods. Based on the framework we have deployed chatbot instances linked on the official web sites of two major German cities. This enables us to collect real user feedback and to evaluate the strengths and weaknesses of our approach.</p><p>The remaining work is structured as follows. In Section 2 we give a brief overview on existing approaches and discuss strengths and weaknesses. Section 3 explains our approach and describes the developed methods. Section 4 discusses the evaluation results. Finally, a summary and outlook on future work is given in Section 5.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Related Work</head><p>In this section, we review related approaches and analyze existing chatbot systems.</p><p>Personal Assistance Bots and Chatbot Frameworks Conversation agents ("Chatbots") have got in the focus of interest in recent years. This can be explained by ubiquity of mobile devices and installed personal assistants informing users about the weather, calendar entries and news as well as allowing users to control smart home devices <ref type="bibr" target="#b1">[2]</ref>. These systems analyze the user input by applying rule sets. Based on the determined user intent information from the calendar or encyclopedias (e.g. Wikipedia), are queried. These systems usually are focused on providing short facts in a direct answer without supporting long dialogs.</p><p>For developing personal agents several frameworks have been developed, such as Amazon Lex ("Alexa") <ref type="foot" target="#foot_0">1</ref> and Google DialogFlow 2 . The core concept used by the systems is the intent. For each intent, several example sentences ("utterances") must be defined. These sentences typically contain slots that are matched with specific user inputs. In order to ensure that the frameworks reliably match the user input, a large number of patterns must be defined for every intent. This typically leads to an explosion of complexity. Thus, the systems are developed for use cases characterized by a rather small number of intents. When defining a new virtual assistant, it is difficult to include existing knowledge bases since they are incompatible with the intent structure of the chatbot frameworks.</p><p>A similar approach for building on premise chatbots is used by the chatbot framework "rasa" <ref type="bibr" target="#b3">[4]</ref>. The framework integrates several natural language analysis tools and a neuronal network that must be trained with annotated sample sentences.</p><p>These frameworks are usually applied for handling a rather small set of questions. Users can train their personal chatbot so that it learns the user wording and adapts to the individual user preferences. In order to ensure a reliable detection of user intents several dozen training examples per intent are needed making this approach not applicable for scenarios characterized by a large collection of intents.</p><p>FAQ Sets and IR-based Approaches Traditionally, lists of frequently asked questions or forums are used for providing answers to questions. In order to cope with large sets of questions, information retrieval-based approaches are used. These approaches are implemented based on an inverted index, enabling the efficient matching of user questions with a huge set of texts <ref type="bibr" target="#b9">[10]</ref>. A high result precision is reached by excluding stop words, reducing words to their stem, and by weighting terms based on a TF-IDF scheme <ref type="bibr" target="#b6">[7]</ref>. In order to optimize the precision of the result set, term weights can be optimized based on relevance feedback <ref type="bibr" target="#b7">[8]</ref> or query expansion techniques can be applied <ref type="bibr" target="#b2">[3]</ref>.</p><p>The advantage of the approach is that existing knowledge bases and FAQ lists can be used for creating a chatbot. The task of handling new questions could be delegated to a human expert who creates a new FAQ entry after answering the question. The disadvantage of this approach is that longer dialogs are not supported. This results often in a lack of context information that leads to a reduced answer precision. The concept of FAQ-based chatbots is used by the chatbot of the city of Vienna<ref type="foot" target="#foot_1">3</ref> or the bot of the Singapore administration <ref type="foot" target="#foot_2">4</ref> .</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Semantic Topic Mapping</head><p>The semantic storage of information based on ontologies and semantic graphs enables a generic, language-independent knowledge representation <ref type="bibr" target="#b4">[5,</ref><ref type="bibr" target="#b8">9]</ref>. Linguistic approaches are applied, such as Named Entity Recognition and Named Entity Disambiguation, linking the natural language user inputs with the nodes in the semantic graph. In a first step, the user input is enriched using a Part-Of-Speech tagger. Detected entities are mapped to the concepts of an ontology. Semantic query languages are then used for querying the requested facts from the knowledge base.</p><p>The advantage of Semantic Topic Mapping is that the representation of facts and the processing of natural user inputs are separated, allowing for existing optimized tools to be utilized. The semantic graphs can incorporate the context resulting in an improved answer precision.</p><p>The disadvantages are that the conversion of text-focused databases into semantic, ontology-based knowledge stores is a complex, time-consuming task. The creation of ontologies and the mapping from texts into ontologies is expensive and requires abstract knowledge about the specific domains. Furthermore, semantic query languages are usually deployed for retrieving a direct answer and do not support longer dialogs.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Discussion</head><p>The existing approaches do not fulfil the requirement for building well-scalable chatbots based on large knowledge collections. The search engines are optimized for key word queries and return documents. Natural, complex dialogs are not supported.</p><p>Systems trained based on annotated question-answer pairs are not applicable for large knowledge collections since the required amount of training data does not exist. Due to the underlying probability models these approaches are often unstable. A retraining of specific questions may reduce the precision for already well-trained question-answer pairs.</p><p>The weaknesses of the existing approaches motivate us to develop a new approach for building chatbots based on existing knowledge collections. Our approach adapts existing knowledge bases in a way that information can be used in a "natural" dialog. This enables us to overcome the weaknesses of existing systems without creating knowledge bases and training data collections from scratch.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Approach</head><p>We develop an architecture that integrates existing databases and components for handling dialogs as well as mapping natural language user questions to knowledge base entries. The system architecture is visualized in Fig. <ref type="figure" target="#fig_0">1</ref>. In the subsequent sections we explain the components and developed methods.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Adaptation of Data to be Suitable for a Chatbot</head><p>The key components of the system are databases describing the information objects. In our concrete use case, we have to manage information about services, locations, and external topics. We split the documents into parts of reasonable size, usually on paragraph level. In order to ensure that the paragraphs are understandable without other paragraphs, references and anaphors need to be resolved (removing the dependencies from other resources). The extracted paragraphs must not be too long to make sure that the information pieces are useful, and that the agent does not answer in long monologs. The paragraphs are enriched with meta-data building the basis for the matching of user questions with answers.</p><p>Structuring services provided by the Public Administration For describing the services, ontologies and meta-data can be used. In Germany, the LeiKa catalog  defines a hierarchy of services offered by the public administration. In addition, keywords for the services are provided containing synonyms and colloquial terms helping to match real user language with the formal administrative language. Due to the broad range of topics in the LeiKa catalog not all ontology nodes are well covered with keywords.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Synonyms and Meta Data</head><p>In a natural dialog, users often use colloquial language. This is a challenge since the used terms differ from the official language used by the administration. Thus, synonymy and colloquial terms must be learned by the system in order to "translate" the user language into the formal language. Colloquial terms such as "paperboard" (German: "Pappe") might be ambiguous and domain dependent. In addition outdated terms or region specific wording must be considered. General synonym collections are usually not enough since they do not provide enough coverage for the specific domain. This requires that these "service keyword" collections must be continuously extended and maintained based on observed dialogs and user feedback.</p><p>For supporting a location-focused search, databases of postal codes, street names and urban district names must be incorporated for handling questions such as "What are the opening hours of the registry office Friedrichstraße."</p><p>Providing Information in Different Levels of Detail Dialogs as well as documents usually start with general information and provide subsequently details for different aspects. This means that the information is stored in a tree-like structure. A user question does not only have to be matched with the right subtree, but with the concrete node. If a user asks "What are the fees for getting a passport", the service "apply for a passport" must be matched as well as the node "fees". Thus, the question is only precisely answered, if both criteria are matched correctly. In order to avoid giving the user incorrect answers, our system asks the user, whether the service has been identified correctly ("Are you interested in getting information about 'apply for a passport' "). This additional question means an additional effort for the user but improves the trust in the systems since the method ensures that the user intent has been identified correctly.</p><p>Handling Dialogs -Considering the Context In chats users find the requested information interactively. This means that users often ask questions related to previous questions, typically focusing on more detailed information. Thus the chatbot must determine for every question whether the new user input should be handled as a follow-up question or whether the user wants to switch to a new topic. In our system we use a state model. If the user already selected a location or a service object, subsequent questions are handled as follow-up questions. If no information can be found based on this assumption, the systems asks the user, whether the user expects follow-up information or wants to switch to a new topic.</p><p>Recommendations Asking the right question is difficult if the domain is new to a user. To address this problem, we implemented a recommender component that suggests questions based on the behavior of other users. This is especially useful to make sure that the user becomes aware of all relevant aspects.</p><p>Detecting Off-Domain Questions Chatbot systems are typically developed for providing answers for one domain; but users often check, how the system handles questions outside the target domain, e.g. Who is the chancellor of Germany or Who will win the National Soccer Championship. Providing detailed answers for every possible question is too complex and too expensive to implement. If the system answers simple off-domain questions correctly, this motivates users to ask more complex questions. In order to ensure a high answer quality, the chatbot system should focus on one domain. We implemented classification algorithms predicting whether a question belongs to the desired domain or the question is out of the scope of the system.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Multi-language Dialogs</head><p>In order to reach a larger number of users a translator component has been developed. It is based on an arbitrary third party translation service such as Microsoft Azure<ref type="foot" target="#foot_4">6</ref> or DeepL<ref type="foot" target="#foot_5">7</ref> . First, the user question is translated from any input language supported by the translation service to the system's main language, which is German in our scenario. The generated answer is then translated back to the user's original input language. Both these steps are entirely transparent to the user. Translations are highly parallelized and aggressively cached. This guarantees a good performance so that the user hardly notices any delay. The quality of the translations depends on how the input text is phrased. Since the backend of the chatbot system uses an IR-based approach, the system deals well even with translations of grammatically incorrect inputs. Due to the use integrated synonym databases the automatically translated user questions are reliably matched with the knowledge base entries.</p><p>Discussion The developed chatbot architecture has been designed to efficiently handle different types of user requests and to deliver detailed answers for a wide spectrum of questions based on existing data collections. The information objects are split into paragraphs and enriched with additional meta-data. A dialog handling components guides the user and ensures that the context is considered when computing answers. We have tuned the system by integrating additional meta-data collections and learning keywords and phrases. The developed system is open for new knowledge sources and can be adapted to additional domains.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Evaluation and Preliminary Results</head><p>We have implemented a conversational bot and deployed the system on the official web portal of two major German cities. We started without official announcements as an additional channel for citizens seeking for information about the services offered by the administration. In the first month we observed a constantly increasing interest in the service. After 6 months, we served ≈ 2500 dialogs per month on one city portal giving us insights in the user preferences and user habits.</p><p>Dialog Analysis Analyzing the dialogs, we found that most users enter questions in complete sentences. In contrast to our expectations that the majority of users would only use keywords, the questions are asked in a way as if a human would be in the chat, even though the system explicitly explains that the chat is operated by a machine. Handling very comprehensive, detailed user inputs is a challenge. If there are too many questions (different intents) in one user input, it is hard for the bot to deliver an answer containing all needed information. In order to handle this problem the chatbot gives the user a hint to focus on one aspect, if the user input is too long. Very long answers from the agent we avoided by restructuring the knowledge databases (in cooperation with responsible persons of the administration) in order to make the information better understandable and suitable for a chat.</p><p>Classifying the Type of User Questions The core of our chatbot system is a large knowledge base. The implemented chatbot systems use the official service database describing all services offered by the city authorities 8 . Since the databases of services and locations are the core of the system, we expected that almost all questions should be related to these knowledge base entries. Classifying the observed dialogs, we found that 55% of the questions are related to services, 15% are related to locations, and about 5% are related to services and topics offered by external administrative offices (e.g., from the federal government). About 5% of the dialogs are general small talk, e.g., questions related to the weather or the name.</p><p>Surprisingly, about 25% of the questions relate to appointment booking, such as how to find appointments fast or what to do if the user cannot find the details of an already booked appointment. When designing the chatbot system we were not aware of the importance of this type of questions. We trained the chatbot based on user feedback in the first weeks after going public. This meant to identify the relevant questions (that could not be answered by the chatbot system yet) and find appropriate answers in discussion with the administration. We observed that typically 250 sample sentences are needed for reliably learning these questions. This underlines that only for a limited question domain this effort is manageable. From the perspective of knowledge management, the rather big fraction of appointment related questions had been an argument for the official service website to put additional clarifications on the web portals in order to reduce the number of questions related to this topic.</p><p>Feedback and Unclear Answers A chat seems to be a natural way of getting information. This also motivates users to give directly feedback to the quality of the answers. Therefore we designed explicit feedback buttons in the system; but the users tend to give feedback in the chat in natural language sentences. This user feedback has been helpful for identifying questions not covered yet by the knowledge base and finding answers that contain confusing information. If no service and no matching FAQs are found matching the user question, we ask the user to reformulate the question. The explicit query reformulations help us to learn synonyms and to understand the wording used by users. The extracted and checked knowledge is used to extend our knowledge base.</p><p>Another important aspect is the handling of praise and complaints. If the user gives feedback within the chat, the chatbot must not answer with "I did not understand your intention", but acknowledge the feedback.</p><p>Multi-Language Support Our chatbot system integrates a machine translation service. This allows users to chat with the system in eight different languages. The user input is translated on-the-fly into German; the answers are translated back from German into the selected user language.</p><p>The multi-language support is new for the administration since almost all information related to the citizen services is only available in German. This means, that offering support in foreign languages is a value adding feature. In the live systems ≈ 7% of the sessions are using the machine translation component.</p><p>A specific challenge in supporting foreign languages is the difficulty in translating domain-specific terms. The translation of user questions into German works rather well for most questions due to the IR-based approach used in the backend. Due to user inputs usually consisting of several words, the translations of the words match well with the German service descriptions. The translation of German service descriptions into a foreign language is more critical. The challenge is to ensure that the automatic translation of the administrative language is understandable by users. In order to address the problem we checked the answers given by the chatbot for the most popular services. In case of unclear translations we manually collected corrections optimized for our scenario.</p><p>Overall, providing multi-language support is a valuable feature in chatbots optimized for the public administration. Users chatting in a foreign language gave positive feedback. Several users remarked that the 115-telephone support in English is very limited; so the chatbot should not refer to the 115-telephone support ("public authority telephone").</p><p>Robot-based User Interfaces The chatbot system has been developed for a traditional text-based chat. In order to improve the visibility of the chatbot project we have also developed a version optimized for a physical robot-based interface. As robot a 1.20 m big robot "Pepper" <ref type="bibr" target="#b5">[6,</ref><ref type="bibr" target="#b0">1]</ref> has been used.</p><p>The new "physical" user interface required several adaptations. We have integrated a voice-to-text service converting the captured speech into text. This introduces a new source of errors since the speech-to-text component sometimes ignores parts of the user input. Thus the backend must be able to handle incomplete sentences. Our IR-based approach for finding relevant answers works in most cases robustly since the question-answer matching is done based on keywords. For small talk for which the question-FAQ mapping (trained on complete sentences) often additional training examples have been needed for the speech-totext component. Moreover, navigational elements such as lists or radio buttons must be optimized for a voice-controlled interface. For instance, users can say "select suggestion two" or "service two" for selecting the second element from a list of suggestions.</p><p>For handling the answers provided by the robot specific optimizations are needed. Very long answers should be provided in smaller parts. It should be possible to interrupt the robot when answering questions in long monologues. Moreover the users may ask the robot to repeat an answer. In text-based chats repeating an answer does not make sense since users could simply scroll up; in a conversation with a robot the query "could you repeat the answer" is rather common.</p><p>Discussion Overall the developed system shows a good performance providing reliable, highly accurate answers related to the wide spectrum of topics. The conversion of existing databases into a format optimized for chats enables "natural" dialogs for a wide spectrum of topics. Nevertheless, we had to add knowledge required for small talk and for answering questions indirectly related to the information objects.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Conclusion and Future Work</head><p>In this work we presented our chatbot framework optimized for answering questions related to services offered by the public administration. Compared with most existing chatbot systems our approach scales well with the size of the chatbot's knowledge. This ensures that the chatbot covers the complete range of entries from the knowledge base. Furthermore our approach allows setting up a new chatbot instance without explicit training data by mapping existing databases to the ontology used by the chatbot. For building good queries from the user question we combine statistic methods (e.g., popularity-based methods) and natural language analysis models (e.g., syn-sets and Part-Of-Speech tagging). The deployed chatbot systems are incrementally optimized by analyzing the user feedback. We extract synonyms by applying Word-2-Vec models and analyzing the input from users when reformulating a query ("could you please rephrase your request"). If there are several answers matching a user request, the relevant answers can be figured out interactively in a dialog.</p><p>The evaluation shows that the deployed systems provide a good answer quality. The retrieval-based approach works robustly with the variety of natural language formulations. The training of the query optimization matching component with real user feedback improves the matching for the most popular services. A big challenge is the handling of off-topic questions. Since the system is optimized for one domain, it is difficult to detect whether a question is offtopic or uses a very uncommon wording. In order to address this problem we plan to build a dataset for learning a classifier. Furthermore, we are working on more sophisticated machine learning methods for extracting relevant patterns from the collected user feedback in order to improve the structure of the dialogs and to optimize the matching precision for fuzzy questions.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. System Architecture</figDesc></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">https://docs.aws.amazon.com/lex/latest/dg/what-is.html</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_1">https://www.wien.gv.at/bot/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_2">https://www.gov.sg/news/content/5-reasons-to-use-the-gov-sg-bot</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_3">http://www.gk-leika.de/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_4">https://azure.microsoft.com/en-us/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="7" xml:id="foot_5">https://www.deepl.com/</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Hello pepper, may i tickle you?: Children&apos;s and adults&apos; responses to an entertainment robot at a shopping mall</title>
		<author>
			<persName><forename type="first">I</forename><surname>Aaltonen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Arvola</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Heikkilä</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Lammi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Procs. of the Companion of the 2017 ACM/IEEE International Conference on Human-Robot Interaction, HRI &apos;17</title>
				<meeting>s. of the Companion of the 2017 ACM/IEEE International Conference on Human-Robot Interaction, HRI &apos;17<address><addrLine>New York, USA</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page" from="53" to="54" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Survey on chatbot design techniques in speech conversation systems</title>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">A</forename><surname>Abdul-Kader</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">J</forename><surname>Woods</surname></persName>
		</author>
		<idno type="DOI">10.14569/IJACSA.2015.060712</idno>
		<ptr target="http://dx.doi.org/10.14569/IJACSA.2015.060712" />
	</analytic>
	<monogr>
		<title level="j">International Journal of Advanced Computer Science and Applications</title>
		<imprint>
			<biblScope unit="volume">6</biblScope>
			<biblScope unit="issue">7</biblScope>
			<biblScope unit="page" from="72" to="80" />
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Agent Technology for Personalized Information Filtering: The PIA-System</title>
		<author>
			<persName><forename type="first">S</forename><surname>Albayrak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Wollny</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Lommatzsch</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Milosevic</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Scalable Computing: Practice and Experience</title>
		<imprint>
			<biblScope unit="volume">8</biblScope>
			<biblScope unit="page" from="29" to="40" />
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<title level="m" type="main">Rasa: Open source language understanding and dialogue management</title>
		<author>
			<persName><forename type="first">T</forename><surname>Bocklisch</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Faulkner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Pawlowski</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Nichol</surname></persName>
		</author>
		<idno type="arXiv">arXiv:1712.05181</idno>
		<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
	<note type="report_type">arXiv preprint</note>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">An agent-based movie recommender system combining the results computed based on heterogeneous semantic datasets</title>
		<author>
			<persName><forename type="first">A</forename><surname>Lommatzsch</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Kille</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Albayrak</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of the 13th GI International Conference on Innovative Internet Community Systems and the Workshop on Autonomous Systems, I2CS &apos;13</title>
				<meeting>of the 13th GI International Conference on Innovative Internet Community Systems and the Workshop on Autonomous Systems, I2CS &apos;13<address><addrLine>Düsseldorf, Germany</addrLine></address></meeting>
		<imprint>
			<publisher>VDI-Verlag</publisher>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<title level="m" type="main">Robots that Talk and Listen: Technology and Social Impact</title>
		<author>
			<persName><forename type="first">J</forename><surname>Markowitz</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2014">2014</date>
			<publisher>Walter de Gruyter</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">A survey on question answering systems with classification</title>
		<author>
			<persName><forename type="first">A</forename><surname>Mishra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">K</forename><surname>Jain</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">J. King Saud Univ. Comput. Inf. Sci</title>
		<imprint>
			<biblScope unit="volume">28</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="345" to="361" />
			<date type="published" when="2016-07">July 2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">The probabilistic relevance framework: BM25 and beyond</title>
		<author>
			<persName><forename type="first">S</forename><surname>Robertson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Zaragoza</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Foundations and Trends in Information Retrieval</title>
		<imprint>
			<biblScope unit="volume">3</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="333" to="389" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Compositional learning of embeddings for relation paths in knowledge base and text</title>
		<author>
			<persName><forename type="first">K</forename><surname>Toutanova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Lin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>-T. Yih</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Poon</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Quirk</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Procs. of the 54th Meeting of the Assoc for Comp. Linguistics</title>
				<meeting>s. of the 54th Meeting of the Assoc for Comp. Linguistics</meeting>
		<imprint>
			<date type="published" when="2016">2016</date>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="page" from="1434" to="1444" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<title level="m" type="main">Text Data Management and Analysis: A Practical Introduction to IR and Text Mining</title>
		<author>
			<persName><forename type="first">C</forename><surname>Zhai</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Massung</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2016">2016</date>
			<publisher>ACM and Morgan</publisher>
			<pubPlace>Claypool, NY, USA</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
