| { | |
| "paper_id": "H86-1006", | |
| "header": { | |
| "generated_with": "S2ORC 1.0.0", | |
| "date_generated": "2023-01-19T03:35:17.139648Z" | |
| }, | |
| "title": "Text Generation for Strategic Computing", | |
| "authors": [ | |
| { | |
| "first": "William", | |
| "middle": [], | |
| "last": "Mann", | |
| "suffix": "", | |
| "affiliation": {}, | |
| "email": "" | |
| }, | |
| { | |
| "first": "Norman", | |
| "middle": [], | |
| "last": "Sondheimer", | |
| "suffix": "", | |
| "affiliation": {}, | |
| "email": "" | |
| } | |
| ], | |
| "year": "", | |
| "venue": null, | |
| "identifiers": {}, | |
| "abstract": "The US military is an information-rich, computer intensive organization. It needs to have easy, understandable access to a wide variety of information. Currently, information is often in obscure computer notations that are only understood after extensive training and practice. Although easy discourse between users and machines is an important objective for any situation, this issue is particularly critical in regards to automated decision aids such as expert system based battle management systems that have to carry on a dialog with a force commander. A commander cain not afford to miss important information, nor is it reasonable to expect force commanders to undergo highly specialized training to understand obscure computer dialects which differ from machine to machine. The great deal of work that has been done in the area of natural language understanding is starting to pay off with the delivery of functional interfaces that interact naturally with the user. Comparatively little, however, has been done in the area of natural language generation. Currently. there is no effective technology for expressing complex computer notations in ordinary English. If there were. computer-based military information could be made more accessible and understandable in a manner less subject to personnel changes. The Text Generation for Strategic Computing project is creating and demonstrating new technology to provide an English-in, English-out interface to computer data to be embodied in a system called Janus. ISI is developing the English-out (text generation) portion of this overall system, a module named Penman. It's initial capability will be demonstrated on a naval database, but most of the techniques are more .general and will be able to be reapplied to other military problems. The end result will be an exciting new capability for the military that produces answers to queries and commands in the form of text that is understandable to any user who understands English.", | |
| "pdf_parse": { | |
| "paper_id": "H86-1006", | |
| "_pdf_hash": "", | |
| "abstract": [ | |
| { | |
| "text": "The US military is an information-rich, computer intensive organization. It needs to have easy, understandable access to a wide variety of information. Currently, information is often in obscure computer notations that are only understood after extensive training and practice. Although easy discourse between users and machines is an important objective for any situation, this issue is particularly critical in regards to automated decision aids such as expert system based battle management systems that have to carry on a dialog with a force commander. A commander cain not afford to miss important information, nor is it reasonable to expect force commanders to undergo highly specialized training to understand obscure computer dialects which differ from machine to machine. The great deal of work that has been done in the area of natural language understanding is starting to pay off with the delivery of functional interfaces that interact naturally with the user. Comparatively little, however, has been done in the area of natural language generation. Currently. there is no effective technology for expressing complex computer notations in ordinary English. If there were. computer-based military information could be made more accessible and understandable in a manner less subject to personnel changes. The Text Generation for Strategic Computing project is creating and demonstrating new technology to provide an English-in, English-out interface to computer data to be embodied in a system called Janus. ISI is developing the English-out (text generation) portion of this overall system, a module named Penman. It's initial capability will be demonstrated on a naval database, but most of the techniques are more .general and will be able to be reapplied to other military problems. The end result will be an exciting new capability for the military that produces answers to queries and commands in the form of text that is understandable to any user who understands English.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Abstract", | |
| "sec_num": null | |
| } | |
| ], | |
| "body_text": [ | |
| { | |
| "text": "This project was put in place at the beginning of FY85 in order to develop the first natural language generation capability robust and capable enough to be used in DARPA's Strategic Computing Program. It is intended that this interface be coupled to the battle management system being developed under DARPA's Fleet Command Center Battle Management Program(FCCBMP). In the first 1.5 years of the effort, we were able to demonstrate the first generation system to produce English from output demands in formal mathematical logic using a broad coverage grammar and an artificial intelligence knowledge base. We have developed the basic technology that will permit the realization of a full text generation system. In the next phase of the work, we will extend text generation from sentences to paragraphs, increase the power of the grammar, dictionary, and planner, expand the knowledge base to cover more fully the battle management problem, optimize and increase the robustness of the software, and tune the resulting system to the Navy problem. Finally, we will deliver our generation system to BBN, Inc, who will combine it with an understanding system for delivery to DARPA and subsequent integration with FCCBMP.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "This report details our approach, Penman's current status, and our plans for future work.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Both understanding and generation components are necessary in an effective information system interface. It is also necessary that the technologies used by these two components be absolutely consistent. If they are not, the embarrassing situation of the interface failing to understand a piece of text which it has just output can occur, causing a lack of confidence in the system by users.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Our Approach", | |
| "sec_num": "2" | |
| }, | |
| { | |
| "text": "In order to alleviate this problem, we are developing Penman in close cooperation with a natural language understanding project at Bolt, Beranek, and Newman Inc. (BBN). This cooperation extends to joint development of knowledge representation software and lexicon design, and work to insure compatibility between the RUS understanding grammar and the Nigel generation grammar.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Our Approach", | |
| "sec_num": "2" | |
| }, | |
| { | |
| "text": "The understanding/generation compatibility effort can be considered the first of our goals for the Penman system. Another is the ability to generate substantial amounts of English text, up to the multiparagraph level. A useful interface should not be restricted to short replies or comments.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Our Approach", | |
| "sec_num": "2" | |
| }, | |
| { | |
| "text": "A third goal is to make Penman as portable and domain independent as possible. There are many knowledge domains available for interface systems, and few specialists to create the interfaces. Thus. we are emphasizing domain independent capabilities over domain dependent ones.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Our Approach", | |
| "sec_num": "2" | |
| }, | |
| { | |
| "text": "Finally. there are many linguistically and computationally significant issues that must be addressed if high quality generation is to be achieved. For example, we are working on improved methods for knowledge representation, vocabulary development, and for using semantics and discourse context to guide the generaiion of text.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Our Approach", | |
| "sec_num": "2" | |
| }, | |
| { | |
| "text": "By the time of this report, the project had created and delivered a Master Lexicon facility, called ML. for vocabulary acquisition and use [Cumming 86a, Cumming 86b, Cumming 86c]. ML is unusual in that it is compatible with the two radically different grammars of English in Janus; the Nigel generation grammar and the Rus understanding grammar. The system features a multi.window bit mapped display which is manipulatable through the keyboard and a mouse. Online documentation is provided for all lexical choices. ML is built to allow for the extension of the Janus lexical system. It is also possible to use ML with other natural language processing systems by replacement of a single data structure.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Accomplishments", | |
| "sec_num": "3" | |
| }, | |
| { | |
| "text": "In addition, work has been done on bringing the Nigel and RUS grammars into compatibility.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Accomplishments", | |
| "sec_num": "3" | |
| }, | |
| { | |
| "text": "Our general goal is the development of natural language generation capabilities. Our vehicle for these capabilities will be a reusable module designed to meet all of a system's needs for generated sentences. The generation module must have an input notation in which demands for expression are represented. This notation should be of general applicability. For example, a good notation ought to be generally useful in a reasoning system. Also, the notation should have a well-defined semantics and the generator has to have some way of interpreting the demands. This interpretation has to be efficient.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Accomplishments", | |
| "sec_num": "3" | |
| }, | |
| { | |
| "text": "In our research, we have chosen to use formal logic as a demand language. Network knowledge-bases are used to define the domain of discourse in order to help the generator interpret the logical forms. And a restricted, hybrid knowledge representation is utilized to analyze demands for expression using the knowledge base [Sondheimer 86 To first order logic, PLF adds restricted quantification, i.e.. the ability to restrict the set quantified over. In addition, we allow for equality and some related quantifiers and operators, such as the quantifier for \"there exists exactly one ...\" (3!). the operator for \"the one thing that ...\" (L). We permit the formation and manipulation of sets. including a predicate for set membership (ELEMENT-OF). And we have some quantifiers and operators based on Habel's 7//operator [Habel 82 ].", | |
| "cite_spans": [ | |
| { | |
| "start": 322, | |
| "end": 336, | |
| "text": "[Sondheimer 86", | |
| "ref_id": null | |
| }, | |
| { | |
| "start": 817, | |
| "end": 826, | |
| "text": "[Habel 82", | |
| "ref_id": null | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Accomplishments", | |
| "sec_num": "3" | |
| }, | |
| { | |
| "text": "Our system's knowledge has been organized in a new way in order to facilitate English expression. Abstract concepts corresponding to the major conceptual categories of English have been defined in NIKL (a KL-ONE dialect) and used to organize the conceptual hierarchy of the domain. By defining concepts such as process, event, quality, relationship and object in this way, fluent English expression is facilitated.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Accomplishments", | |
| "sec_num": "3" | |
| }, | |
| { | |
| "text": "KL-TWO is a hybrid knowledge representation system that uses NIKL's formal semantics: KL.TWO links another reasoner, PENNI to NIKL. For our purposes. PENNI can be viewed as restricted to reasoning using propositional logic.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Accomplishments", | |
| "sec_num": "3" | |
| }, | |
| { | |
| "text": "We translate a logical form into an equivalent KL-TWO structure. All predications appearing in the logical form are put into the PENNI database as assertions. A separate tree is created which reflects the variable scoping. Separate scopes are kept for the range restriction of a quantification and its predication.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Accomplishments", | |
| "sec_num": "3" | |
| }, | |
| { | |
| "text": "The Nigel grammar and generator realizes the functional systemic framework at the\" level of sentence generation. Within this framework, language is viewed as offering a set of grammatical choices to its speakers. Speakers make their choices based on the information they wish to convey and the discourse context they find themselves in. Nigel captures the first of these notions by organizing minimal sets of choices into systems. The grammar is actually just a collection of these systems. The factors the speaker considers in evaluating his communicative goal are shown by questions called inquiries inside of the chooser that is associated with each system. A choice alternative in a system is chosen according to the responses to one or more of these inquiries. It is these inquiries which we have implemented.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Accomplishments", | |
| "sec_num": "3" | |
| }, | |
| { | |
| "text": "Our implementation of Nigel's inquiries using the connection and scope structures with the NIKL upper structure is fairly straightforward. Since the logical forms reflecting the world view are in the highest level of the NIKL model, the information decomposition inquiries use these structures to do search and retrieval. With all of the predicates in the domain specializing concepts in the functional systemic level of the NIKL model, information characterization inquiries that consider aspects of the connection structure can test for the truth of appropriate PENNI propositions. The inquiries that relate to information presented in the quantification structure of the logical form will search the scope structure. Finally, to supply lexical entries, we associate lexical entries with NIKL concepts as attached data and use the retrieval methods of PENNI and NIKL to retrieve the appropriate terms.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Accomplishments", | |
| "sec_num": "3" | |
| }, | |
| { | |
| "text": "Although we have done some generation using the BBN naval knowledge base, our most extensive experience comes from the Consul knowledge domain of computer mail and calendars [Kaczmarek. Mark, and Sondheimer 83] . Using the developments above, translation from first-order logic to English organized by NIKL has been demonstrated for a wide variety of sentence types. Table 3 shows a series of independent sentences that Penman is now able to generate. We have arranged and labeled them to show how they might enter into computer database dialogue. Paraphrases in <brackets> show corresponding sentences of the type that will be generated from Naval domain knowledge.", | |
| "cite_spans": [ | |
| { | |
| "start": 174, | |
| "end": 191, | |
| "text": "[Kaczmarek. Mark,", | |
| "ref_id": null | |
| }, | |
| { | |
| "start": 192, | |
| "end": 210, | |
| "text": "and Sondheimer 83]", | |
| "ref_id": null | |
| } | |
| ], | |
| "ref_spans": [ | |
| { | |
| "start": 367, | |
| "end": 374, | |
| "text": "Table 3", | |
| "ref_id": null | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "Accomplishments", | |
| "sec_num": "3" | |
| }, | |
| { | |
| "text": "Besides the technology described above, work has been done on aspects of discourse modeling. This included a study of object description and an initial noun phrase planner, which space does not allow us to detail.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Accomplishments", | |
| "sec_num": "3" | |
| }, | |
| { | |
| "text": "In order to produce the texts that are needed in a user assistance facility, work is under way to apply Rhetorical Structure Theory to text planning. A procedure has been developed which can design structures for paragraph-length texts given information about the text goal and communication situation.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Accomplishments", | |
| "sec_num": "3" | |
| }, | |
| { | |
| "text": "In the next phase of our effort, Penman will be delivered to BBN, integrated into Janus, and demonstrated in an extensive series of laboratory exercises. This version of Penman will support coordinated English input and output, paraphrasing, and user assistance, as well as constructive rhetorical structure theory to create descriptive texts [Mann 84 ].", | |
| "cite_spans": [ | |
| { | |
| "start": 343, | |
| "end": 351, | |
| "text": "[Mann 84", | |
| "ref_id": null | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Future Effort", | |
| "sec_num": "4" | |
| }, | |
| { | |
| "text": "For a machine to create fluent English texts, several problems of text organization and presentation must be solved. We will design, implement and demonstrate two kinds of new text planning processes. One will be a planner for gross organization of text based on rhetorical structure theory, and the other a low level planner for sentence configurations. In addition, we will examine the expert system explanation functionality necessary within FCCBMP and will design a text planner to meet those needs. ", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Future Effort", | |
| "sec_num": "4" | |
| }, | |
| { | |
| "text": "11.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "10.", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "We also plan to develop enhancements to the basic interface to Penman. As part of Janus, BBN plans to develop methods for translating English inputs into a higher order predicate calculus form. In addition, the logical form will be manipulated inside the BBN understanding component to reflect database organization, expressions in this form are expected to be much more complex than the direct expressions of the corresponding English, requiring multiple sentence expression. Penman will be extended so that it can express these complex forms in English.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "12.", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Following successful completion of initial laboratory testing, Penman will be delivered to NOSC for knowledge base development and testing. This Penman will have a basic text generation capability with only limited capability for responding to the knowledge of the user and the state of the user-machine interaction. In subsequent years, these basic capabilities will be extensively expanded to provide a much more useful interface, with particular development in the areas of user assistance, ability of the system to understand the user's knowledge and expectations, and needs for expert system explanation and user dialogue, as described below.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "12.", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Development of extensions is required in the area of user assistance functionality. Text generation can assist the user by explaining system actions and objects, and by clarifying its interpretation of incoming English. These capabilities must be integrated into the Janus interface in a natural, easy-touse form. We expect to demonstrate increased user assistance functionality as time goes on. Development of extensions is also required in the area of responsiveness to users' knowledge and expectations. This includes making the system aware of the ongoing topics and issues, what the user has already been told, and what he can be expected to know without being told. This in turn involves more extensive use of inference. It also requires implementing a notion of the state of the dialogue -what things are in attention, what interactions are in process and what has been interrupted and suspended.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "12.", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Penman is scheduled for use in an expert-system explanation context whose details are yet to be determined. We will study what functionality is required in FCCBMP. The study will lead to a design of code for this use of Penman. Implementation and demonstration of full functionality are expected following the user assistance work.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "12.", | |
| "sec_num": null | |
| } | |
| ], | |
| "back_matter": [], | |
| "bib_entries": { | |
| "BIBREF0": { | |
| "ref_id": "b0", | |
| "title": "Design of a Master Lexicon, USC/Information Sciences Institute", | |
| "authors": [ | |
| { | |
| "first": "Susanna", | |
| "middle": [], | |
| "last": "Cumming", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1986, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Susanna Cumming, Design of a Master Lexicon, USC/Information Sciences Institute, Marina del Rey,CA, Technical Report ISI/RR-85-163, February 1986.", | |
| "links": null | |
| }, | |
| "BIBREF1": { | |
| "ref_id": "b1", | |
| "title": "A Guide to Lexical Acquisition in the JANUS System, USC/Information Sciences Institute", | |
| "authors": [ | |
| { | |
| "first": "Susanna", | |
| "middle": [], | |
| "last": "Cumming", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "Robert", | |
| "middle": [], | |
| "last": "Albano", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1986, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Susanna Cumming, Robert Albano, A Guide to Lexical Acquisition in the JANUS System, USC/Information Sciences Institute, Marina del Rey,CA, Technical Report ISI/RR-85-162, February 1986.", | |
| "links": null | |
| }, | |
| "BIBREF2": { | |
| "ref_id": "b2", | |
| "title": "The Lexicon in Text Generation, USC/Information Sciences Institute", | |
| "authors": [ | |
| { | |
| "first": "Susanna", | |
| "middle": [], | |
| "last": "Cumming", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1986, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Susanna Cumming, The Lexicon in Text Generation, USC/Information Sciences Institute, Marina del Rey,CA, Technical Report ISI/RR-86-168, 1986. Presented at The Workshop on Automating the Lexicon, Pisa, Italy, May, 1986.", | |
| "links": null | |
| }, | |
| "BIBREF3": { | |
| "ref_id": "b3", | |
| "title": "Referential nets with attributes", | |
| "authors": [ | |
| { | |
| "first": "Christopher", | |
| "middle": [], | |
| "last": "Habel", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1982, | |
| "venue": "Proc. COLING-82", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Christopher Habel, \"Referential nets with attributes,\" in Horecky (ed.), Proc. COLING-82, North-Holland, Amsterdam, 1982.", | |
| "links": null | |
| }, | |
| "BIBREF4": { | |
| "ref_id": "b4", | |
| "title": "Recent Developments in NIKL", | |
| "authors": [ | |
| { | |
| "first": "T", | |
| "middle": [], | |
| "last": "Kaczmarek", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "R", | |
| "middle": [], | |
| "last": "Bates", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "G", | |
| "middle": [], | |
| "last": "Robins", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1986, | |
| "venue": "AAAI-86, Proceedings of the National Conference on Artificial Intelligence, AAAI", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Kaczmarek 86] T. Kaczmarek, R. Bates, G. Robins, \"Recent Developments in NIKL,\" in AAAI-86, Proceedings of the National Conference on Artificial Intelligence, AAAI, Philadelphia, PA, August 1986.", | |
| "links": null | |
| }, | |
| "BIBREF5": { | |
| "ref_id": "b5", | |
| "title": "The Consul/CUE Interface: An Integrated Interactive Environment", | |
| "authors": [ | |
| { | |
| "first": "Mark", | |
| "middle": [], | |
| "last": "Kaczmarek", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "]", | |
| "middle": [ | |
| "T" | |
| ], | |
| "last": "Sondheimer 83", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "W", | |
| "middle": [], | |
| "last": "Kaczmarek", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "N", | |
| "middle": [], | |
| "last": "Mark", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "", | |
| "middle": [], | |
| "last": "Sondheimer", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1983, | |
| "venue": "Proceedings of CHI '83 Human Factors in Computing Systems", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "98--102", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Kaczmarek, Mark, and Sondheimer 83] T. Kaczmarek, W. Mark, and N. Sondheimer, \"The Consul/CUE Interface: An Integrated Interactive Environment,\" in Proceedings of CHI '83 Human Factors in Computing Systems, pp. 98-102, ACM, December 1983.", | |
| "links": null | |
| }, | |
| "BIBREF6": { | |
| "ref_id": "b6", | |
| "title": "Discourse Structures for Text Generation, USC/Information Sciences Institute", | |
| "authors": [ | |
| { | |
| "first": "W", | |
| "middle": [], | |
| "last": "Mann", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1984, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Mann, W., Discourse Structures for Text Generation, USC/Information Sciences Institute, Marina del Rey, CA, Technical Report RR-84-127, February 1984.", | |
| "links": null | |
| }, | |
| "BIBREF7": { | |
| "ref_id": "b7", | |
| "title": "Nigeh A Systemic Grammar for Text Generation. USC/Information Sciences Institute", | |
| "authors": [ | |
| { | |
| "first": "C", | |
| "middle": [], | |
| "last": "Mann & Matthiessen 83] William", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "M", | |
| "middle": [ | |
| "I M" | |
| ], | |
| "last": "Mann & Christian", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "", | |
| "middle": [], | |
| "last": "Matthiessen", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1983, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Mann & Matthiessen 83] William C. Mann & Christian M.I.M. Matthiessen, Nigeh A Systemic Grammar for Text Generation. USC/Information Sciences Institute, Technical Report ISI/RR-83.105, Feb 1983.", | |
| "links": null | |
| }, | |
| "BIBREF8": { | |
| "ref_id": "b8", | |
| "title": "A Logical-Form and Knowledge-Base Design for Natural Language Generation", | |
| "authors": [ | |
| { | |
| "first": "Norman", | |
| "middle": [], | |
| "last": "Sondheimer", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "Bernhard", | |
| "middle": [], | |
| "last": "Nebel", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1986, | |
| "venue": "AAAI-86, Proceedings of the National Conference on Artificial Intelligence, AAAI", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Norman Sondheimer, Bernhard Nebel, \"A Logical-Form and Knowledge-Base Design for Natural Language Generation.\" in AAAI-86, Proceedings of the National Conference on Artificial Intelligence, AAAI, August 1986.", | |
| "links": null | |
| }, | |
| "BIBREF9": { | |
| "ref_id": "b9", | |
| "title": "Penman's Logical Language, USC/Information Sciences Institute", | |
| "authors": [], | |
| "year": 1985, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "[USC/ISI 85] Penman's Logical Language, USC/Information Sciences Institute, Marina del Rey, CA. 1985.", | |
| "links": null | |
| }, | |
| "BIBREF10": { | |
| "ref_id": "b10", | |
| "title": "The Restricted Language Architecture of a Hybrid Representation System", | |
| "authors": [ | |
| { | |
| "first": "M", | |
| "middle": [], | |
| "last": "Vilain", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1985, | |
| "venue": "Proceedings of the Ninth International Joint Conference on Artificial Intelligence", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "547--551", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "M. Vilain, \"The Restricted Language Architecture of a Hybrid Representation System.\" in Proceedings of the Ninth International Joint Conference on Artificial Intelligence, pp. 547-551. LOS Angeles, CA, August 1985.", | |
| "links": null | |
| } | |
| }, | |
| "ref_entries": { | |
| "TABREF1": { | |
| "num": null, | |
| "text": "Sentences from Penman 1. User: What is the read status of the message which was sent by Jones? <What is the readiness of the ship deployed by CINCPACFLT?> 2. System: Message 40 is unread. <The Nimitz is C4.> 3. User: Are any messages which were sent by Jones in the tape file? <Are any ships, deployed by CINCPACFLT in the Atlantic fleet?> 4. User: Are any messages which were sent by Jones in the old ISI tape file which Smith has? <Are any ships deployed by CINCPACFLT in the new battle group which Spivak You deleted the message, then you asked me to display it. <You deleted Sail Plan 33, then you asked me to display it.> .", | |
| "html": null, | |
| "content": "<table><tr><td>has?></td></tr><tr><td>5. System: Yes. <Yes.></td></tr><tr><td>6. System: Do you want me to display the read status of the messages? <Do you want me to</td></tr><tr><td>display the readiness of the ships?></td></tr><tr><td>7. User: No. <No.></td></tr><tr><td>8. System: There are messages which were sent by Jones. <There are ships which were</td></tr><tr><td>deployed by CINCPACFLT.></td></tr><tr><td>System: However, the tape is in use. <However, the battle group is en route.></td></tr><tr><td>User: Show me Message 40. <Show me the JFK.></td></tr><tr><td>User: Did Smith send any messages? <Did the JFK send any CASREPs?></td></tr><tr><td>System: Message 45 was sent by Smith. <CASREP 45 was sent by the JFK.></td></tr><tr><td>13. User: Did Smith schedule his meeting with me in New York? <Did the JFK schedule its</td></tr><tr><td>port visit in San Diego?></td></tr><tr><td>14. System: Yes. <Yes.></td></tr><tr><td>15. User: What does the window show? <What does the map show?></td></tr><tr><td>16. System: The window shows a message which was sent by Jones. <The map shows a sail</td></tr><tr><td>plan which was sent by CINCPAC></td></tr><tr><td>17. System: The window shows a request by Jones. <The map shows a request which was</td></tr><tr><td>sent by CINCPACFLT.></td></tr><tr><td>18. User: Did I create the window? <Did I create the map?></td></tr><tr><td>19. System: The window was created when you asked me to display Message 50. <The map</td></tr><tr><td>was created when you asked me to display Sail Plan 33.></td></tr><tr><td>20. System:</td></tr></table>", | |
| "type_str": "table" | |
| } | |
| } | |
| } | |
| } |