<?xml version="1.0"?><!DOCTYPE article SYSTEM "/project/take/software/searchbench_offline_processing/paperxml_generator/aclextractor/src/python/../resource/dtd/paperxml.dtd"><article><header><firstpageheader><page local="1"/><title>Multi-lingual Translation of Spontaneously Spoken Language in a Limited Domain</title><author surname="Lavie" givenname="Alon"><org  name="Carnegie Mellon University" country="USA" city="Pittsburgh"/></author><author surname="Gates" givenname="Donna"><org  name="Carnegie Mellon University" country="USA" city="Pittsburgh"/></author><author surname="Gavalda" givenname="Marsal"><org  name="Carnegie Mellon University" country="USA" city="Pittsburgh"/></author><author surname="Mayfield" givenname="Laura"><org  name="Carnegie Mellon University" country="USA" city="Pittsburgh"/></author><author surname="Waibel" givenname="Alex"><org  name="Carnegie Mellon University" country="USA" city="Pittsburgh"/></author><author surname="Levin" givenname="Lori"><org  name="Carnegie Mellon University" country="USA" city="Pittsburgh"/></author></firstpageheader><frontmatter><p><b>Multi-lingual Translation of Spontaneously Spoken Language</b></p><p><b>in a Limited Domain</b></p><p><b>Alon Lavie, Donna Gates, Marsal Gavaldà, Laura Mayfield, Alex Waibel and Lori Levin</b></p><p>Center for Machine Translation Carnegie Mellon University 5000 Forbes Ave., Pittsburgh, PA 15213 <b>email : </b>lavie@cs.cmu.edu</p></frontmatter><abstract>JANUS is a multi-lingual speech-to-speech translation system designed to facilitate communication between two parties engaged in a spontaneous con­versation in a limited domain. In an attempt to achieve both robustness and translation accuracy we use two differ­ent translation components: the GLR module, designed to be more accu­rate, and the Phoenix module, designed to be more robust. We analyze the strengths and weaknesses of each of the approaches and describe our work on combining them. Another recent focus has been on developing a detailed end-to-end evaluation procedure to measure the performance and effectiveness of the system. We present our most recent Spanish-to-English performance evalua­tion results. </abstract></header><body><section number="1" title="Introduction"><p>JANUS is a multi-lingual speech-to-speech trans­lation system designed to facilitate communica­tion between two parties engaged in a sponta­neous conversation in a limited domain. In this paper we describe the current design and perfor­mance of the machine translation module of our system. The analysis of spontaneous speech re­quires dealing with problems such as speech dis-fluencies, looser notions of grammatically and the lack of clearly marked sentence boundaries. These problems are further exacerbated by errors of the speech recognizer. We describe how our machine translation system is designed to effectively han­dle these and other problems. In an attempt to achieve both robustness and translation accu­racy we use two different translation components: the GLR module, designed to be more accurate, and the Phoenix module, designed to be more ro­bust. Both modules follow an interlingua-based approach. The translation modules are designed to be language-independent in the sense that they each consist of a general processor that applies in­dependently specified knowledge about different languages. This facilitates the easy adaptation of the system to new languages and domains. We an­alyze the strengths and weaknesses of each of the translation approaches and describe our work on combining them. Our current system is designed to translate spontaneous dialogues in the Schedul­ing domain, with English, Spanish and German as both source and target languages. A recent focus has been on developing a detailed end-to-end eval­uation procedure to measure the performance and effectiveness of the system. We describe this pro­cedure in the latter part of the paper, and present our most recent Spanish-to-English performance evaluation results.</p></section><section number="2" title="System Overview"><p>The JANUS System is a large scale multi-lingual speech-to-speech translation system designed to facilitate communication between two parties en­gaged in a spontaneous conversation in a limited domain. A diagram of the architecture of the sys­tem is shown in Figure 1. The system is com­posed of three main components: a speech recog­nizer, a machine translation (MT) module and a speech synthesis module. The speech recognition component of the system is described elsewhere (Woszczyna et al. 1994). For speech synthesis, we use a commercially available speech synthesizer.</p><p>The MT module is composed of two separate translation sub-modules which operate indepen­dently. The first is the GLR module, designed to be more accurate. The second is the Phoenix module, designed to be more robust. Both mod­ules follow an interlingua-based approach. The source language input string is first analyzed by a parser, which produces a language-independent interlingua content representation. The interlin-gua is then passed to a generation component, which produces an output string in the target lan­guage.</p><p>The discourse processor is a component of the GLR translation module. It disambiguates the speech act of each sentence, normalizes temporal<page local="2"/></p><doubt alpha="0.0" length="3" tooSmall="False" monospace="0.0">442</doubt><p>Speech in Source Language</p><p><b>GLR* Parser</b> <b>Phoenix Parser</b> <b>Discourse Processor</b></p><p>ILT Feature Structure</p><p>Discourse Memory &amp; , Calendar</p><p>Frame-Slot Structure</p><p>Text in Target Language</p><p>Speech in Target Language</p><p>Figure 1: <b>The JANUS System</b> expressions, and incorporates the sentence into a discourse plan tree. The discourse processor also updates a calendar which keeps track of what the speakers have said about their schedules. The dis­course processor is described in greater detail else­where (Rosé et al. 1995).</p></section><section number="3" title="The GLR Translation Module"><p>The GLR* parser (Lavie and Tomita 1993; Lavie 1994) is a parsing system based on Tomita's Gen­eralized LR parsing algorithm (Tomita 1987). The parser skips parts of the utterance that it cannot incorporate into a well-formed sentence structure. Thus it is well-suited to domains in which non-grammaticality is common. The parser conducts a search for the maximal subset of the original input that is covered by the grammar. This is done using a beam search heuristic that limits the combinations of skipped words considered by the parser, and ensures that it operates within feasible time and space bounds.</p><p>The GLR* parser was implemented as an ex­tension to the GLR parsing system, a unification-based practical natural language system (Tomita 1990). The grammars we develop for the JANUS system are designed to produce feature struc­tures that correspond to a frame-based language-independent representation of the meaning of the input utterance. For a given input utterance, the parser produces a set of interlingua texts, or ILTs.</p><p>The main components of an ILT are the speech act (e.g., suggest, accept, reject), the sentence type (e.g., state, query-ii, fragment), and the main semantic frame (e.g., free, busy). An ex­ample of an ILT is shown in Figure 2. A detailed ILT Specification was designed as a formal de­scription of the allowable ILTs. All parser output must conform to this ILT Specification. The GLR unification based formalism allows the grammars to construct precise and very detailed ILTs. This in turn allows the GLR translation module to pro­duce highly accurate translations for well-formed input.</p><p>The GLR* parser also includes several tools de­signed to address the difficulties of parsing spon­taneous speech. To cope with high levels of am­biguity, the parser includes a statistical disam­biguation module, in which probabilities arc at­tached directly to the actions in the LR parsing table. The parser can identify sentence bound­aries within each hypothesis with the help of a statistical method that determines the probabil­ity of a boundary at each point in the utterance. The parser must also determine the "best" parse from among the different parsable subsets of an input. This is done using a collection of parse evaluation measures which are combined into an integrated heuristic for evaluating and ranking the parses produced by the parser. Additionally, a parse quality heuristic allows the parser to self-<page local="3"/></p><doubt alpha="0.0" length="3" tooSmall="False" monospace="0.0">443</doubt><table class="main" frame="box" rules="all" border="1" regular="False"><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p><b>Speech Recognizer</b></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr></table><table class="main" frame="box" rules="all" border="1" regular="False"><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p><b>GenKit Generator</b></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr></table><table class="main" frame="box" rules="all" border="1" regular="False"><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p><b>Phoenix Generator</b></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr></table><table class="main" frame="box" rules="all" border="1" regular="False"><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p><b>Speech Sythesizer</b></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr></table><doubt alpha="57.8" length="64" tooSmall="False" monospace="0.0">((frame *free) ( who ( (frame *i )}) (when ((frame *simple-time)</doubt><p>(day<b>-of-week </b>Wednesday)</p><p><b>(time-of-day morning))) ( a-speech-act (*tnultiple* *suggest *accept)) (sentence-type +state)))</b> <b>Sentence:</b><b> I could do it Wednesday morning too.</b></p><figure caption="Figure 2: An Example ILT"></figure><p>judge the quality of the parse chosen as best, and to detect cases in which important information is likely to have been skipped.</p><p>Target language generation in the GLR module is done using GenKit (Tomita and Nyberg 1988), a unification-based generation system. With well-developed generation grammars, GenKit results in very accurate translation for well-specified ILTs.</p></section><section number="4" title="The Phoenix Translation Module"><p>The JANUS Phoenix translation module (May-field et al. 1995) is an extension of the Phoenix Spoken Language System (Ward 1991; Ward 1994). The translation component consists of a parsing module and a generation module. Trans­lation between any of the four source languages (English, German, Spanish, Korean) and five tar­get languages (English, German, Spanish, Korean, Japanese) is possible, although we currently focus only on a few of these language pairs.</p><p>Unlike the GLR method which attempts to con­struct a detailed ILT for a given input utterance, the Phoenix approach attempts to only identify the key semantic concepts represented in the ut­terance and their underlying structure. Whereas GLR* is general enough to support both seman­tic and syntactic grammars (or some combination of both types), the Phoenix approach was specifi­cally designed for semantic grammars. Grammat­ical constraints are introduced at the phrase level (as opposed to the sentence level) and regulate semantic categories. This allows the ungrammat-icalities that often occur between phrases to be ignored and reflects the fact that syntactically in­correct spontaneous speech is often semantically well-formed.</p><p>The parsing grammar specifies patterns which represent concepts in the domain. The patterns are composed of words of the input string as well as other tokens for constituent concepts. Elements (words or tokens) in a pattern may be specified as optional or repeating (as in a Klcene star mecha­nism). Each concept, irrespective of its level in the hierarchy, is represented by a separate grammar file. These grammars are compiled into Recursive Transition Networks (RTNs).</p><p>The interlingua meaning representation of an input utterance is derived directly from the parse tree constructed by the parser, by extracting the represented structure of concepts. This represen­tation is usually less detailed than the correspond­ing GLR ILT representation, and thus often re­sults in a somewhat less accurate translation. The set of semantic concept tokens for the Scheduling domain was initially developed from a set of 45 example English dialogues. Top-level tokens, also called slots, represent speech acts, such as sugges­tion or agreement. Intermediate-level tokens dis­tinguish between points and intervals in time, for example; lower-level tokens capture the specifics of the utterance, such as days of the week, and represent the only words that are translated di­rectly via lookup tables.</p><p>The parser matches as much of the input ut­terance as it can to the patterns specified by the RTNs. Out-of-lexicon words are ignored, unless they occur in specific locations where open con­cepts are permitted. A word that is already known to the system, however, can cause a concept pat­tern not to match if it occurs in a position un­specified in the grammar. A failed concept docs not cause the entire parse to fail. The parser can ignore any number of words in between top-level concepts, handling out-of-domain or otherwise un­expected input. The parser has no restrictions on the order in which slots can occur. This can cause added ambiguity in the segmentation of the utterance into concepts. The parser uses a dis­ambiguation algorithm that attempts to cover the largest number of words using the smallest num­ber of concepts.</p><p>Figure 3 shows an example of a speaker ut­terance and the parse that was produced using the Phoenix parser. The parsed speech recog­nizer output is shown with unknown (-) and un­expected (*) words marked. These segments of the input were ignored by the parser. The rele­vant concepts, however, are extracted, and strung together they provide a general meaning represen­tation of what the speaker actually said.</p><p>Generation in the Phoenix module is accom­plished using a simple strategy that sequentially generates target language text for each of the top level concepts in the parse analysis. Each con­cept has one or more fixed phrasings in the target language. Variables such as times and dates arc extracted from the parse analysis and translated directly. The result is a meaningful translation, but can have a telegraphic feel.</p></section><section number="5" title="Combining the GLR and"><p><b>Phoenix Translation Modules</b></p><subsection number="5.1" title="Strengths and Weaknesses of the Approaches"><p>As already described, both the GLR* parser and the Phoenix parser were specifically designed to handle the problems associated with analyzing spontaneous speech.   However, each of the ap-<page local="4"/></p><doubt alpha="0.0" length="3" tooSmall="False" monospace="0.0">444</doubt><p><b>Original uttoraucc:</b></p><p><b>SI QUE TE PARECE TENCH) EL MARTES DIECIOCHO Y EL MIERCOLES DIECINUEVE LIBRES TOIK) EL IMA PODR1AMOS IR DE MÂTINÉ O SEA EN LA TARDE VER EL LA PELKTILA</b> <b>(Roughly " </b><i>Yes what do you think I have.</i><i> Tuesday the teenth and Wednesday the nineteenth free ail day we eouid </i><b><i>ijo </i></b><i>see the matinée so in the afternoon see the the movie.'<footnote anchor="1"/> )</i> <b>As decoded by tho recognizer:</b><b></b></p><p><b>%NOISE% Sil QUE1 TE PARECE %NOISE% TENCJO EL MARTES niECIOCIIO Y EL MIK1RCOLES DIECINUEVE LIBRES </b>TOnO <b>EL 1)11 A PODRI1AMOS </b>IR <b>1)10 MATINEl %NOISE% O SKA LA TARDE A VER LA</b> <b>% &lt; S&gt; </b><i>ml </i><b>que 1 t&lt;:</b><b> parece ten go el martes dioeioclio y e| mielrcoles diecinueve libres todo el dila pod ri 1 amos *IR + DE -MATINEl o sea la tarde a ver LA %&lt;/S&gt;</b> <b>Parse Troc (= Semantic Representation):</b><b></b></p><doubt alpha="85.7" length="7" tooSmall="False" monospace="0.0">Parsed:</doubt><doubt alpha="56.5" length="23" tooSmall="False" monospace="0.0">[respond] ( [yes](Sil))</doubt><doubt alpha="65.5" length="29" tooSmall="False" monospace="0.0">[yourtuni] ( QUK1 TE PARECE )</doubt><doubt alpha="55.9" length="229" tooSmall="False" monospace="0.0">[give info] ( [my availability] ( TENCiO [temp'loc] ( [temporal] ( [point] ( [date] ( EL [d'o'w] ( MARTES )) [date] ( [dayord] ( DIECJIOCHO ) [conj] ( Y ) EL [d'o'w] ( MIE1RCOLES )) [date] ( [day ord] ( DIECINUEVE ))))) LIHRES ))</doubt><doubt alpha="65.9" length="44" tooSmall="False" monospace="0.0">[give'info] ( [my availability] ( [temp loc]</doubt><doubt alpha="56.9" length="51" tooSmall="False" monospace="0.0">( [temporal] ( [range] ( [entire] ( TODQ )EL [unit]</doubt><doubt alpha="41.0" length="39" tooSmall="False" monospace="0.0">( [t'unit] ( 1)11 A )))))I»ODRIlAMOS ))</doubt><doubt alpha="56.2" length="105" tooSmall="False" monospace="0.0">[suggest] ( [suggest'meeting] ( [temp'loc] ( [temporal] ( O SEA [point] ( LA [t'o'd] ( TARDE ))))A VER ))</doubt><p><b>Generated:</b></p><p><b>English &lt; Yes what do you think? I could meet Tuesday eighteenth and Wednesday the nineteenth 1 could meet the whole day do you want to try to get together in the afternoon&gt;</b></p><figure caption="Figure 3: A Phoenix Spanish to English Transla­tion Example"></figure><p>proaches has some clear strengths and weaknesses.</p><p>Although designed to cope with speech disfluen-cies, GLR* can gracefully tolerate only moderate levels of deviation from the grammar. When the input is only slightly ungrammatical, and contains relatively minor disfluencies, GLR* produces pre­cise and detailed ILTs that result in high quality translations. The GLR* parser has difficulties in parsing long utterances that are highly dislluent, or that significantly deviate from the grammar. In many such cases, GLR* succeeds to parse only a small fragment of the entire utterance, and im­portant input segments end up being skipped. <footnote anchor="1"/>Phoenix is significantly better suited to analyzing such utterances. Because Phoenix is capable of skipping over input segments that do not corre­spond to any top level semantic concept, it can far better recover from out-of-domain segments in the input, and "restart" itself on an in-domain segment that follows. However, this sometimes re­sults in the parser picking up and mis-translating a small parsable phrase within an out-of-domain segment. To handle this problem, we are attempt­ing to develop methods for automatically detect­ing out-of-domain segments in an utterance (see section 7).</p><footnote label="1">Recent work on a method for pre-breaking the utterance at sentence boundaries prior to parsing have significantly reduced this problem.</footnote><p>Because the Phoenix approach ignores small function words in the input, its translation results are by design bound to be less accurate. However, the ability to ignore function words is of great ben­efit when working with speech recognition output, in which such words are often mistaken. By keying on high-confidence words Phoenix fakes advan­tage of the strengths of the speech decoder. At the current time, Phoenix uses only very simple dis­ambiguation heuristics, does not employ any dis­course knowledge, and does not have a mechanism similar to the parse quality heuristic of GLR*, which allows the parser to self-assess the quality of the produced result.</p></subsection><subsection number="5.2" title="Combining the Two Approaches"><p>Because each of the two translation methods ap­pears to perform better on different types of utter­ances, they may hopefully be combined in a way that takes advantage of the strengths of each of them. One strategy that we have investigated is to use the Phoenix module as a back-up to the GLR module. The parse result of GLR* is trans­lated whenever it is judged by the parse quality heuristic to be "Good" . Whenever the parse result from GLR* is judged as "Bad", the translation is generated from the corresponding output of the Phoenix parser. Results of using this combination scheme are presented in the next section. We are in the process of investigating some more sophisti­cated methods for combining the two translation approaches.</p></subsection></section><section number="6" title="Evaluation"><subsection number="6.1" title="The Evaluation Procedure"><p>In order to assess the overall effectiveness of the two translation components, we developed a de­tailed end-to-end evaluation procedure (Gates et al. 199(5). We evaluate the translation modules on both transcribed and speech recognized input. The evaluation of transcribed input allows us to assess how well our translation modules would function with "perfect" speech recognition. Test­ing is performed on a set of "unseen" dialogues, that were not used for developing the translation modules or training the speech recognizer.</p><p>The translation of an utterance is manually evaluated by assigning it a grade or a set of grades based on the number of sentences in the utter­ance. The utterances are broken down into sen­tences for evaluation in order to give more weight to longer utterances, and so that utterances con­taining both in and out-of-domain sentences can be judged more accurately.</p><p>Each sentence is classified first as either relevant to the scheduling domain (in-domain) or not rclevant to the scheduling domain (out-of-domain).<page local="5"/> Each sentence is then assigned one of four grades for translation quality: (1) Perfect - a lluent trans­lation with all information conveyed; (2) OK -all important information translated correctly but some unimportant details missing, or the transla­tion is awkward; (3) Bad - unacceptable transla­tion; (4) Recognition Error - unacceptable trans­lation due to a speech recognition error. These grades are used for both in-domain and out-of-domain sentences. However, if an out-of-domain sentence is automatically detected as such by the parser and is not translated at all, it is given an "OK" grade. The evaluations are performed by one or more independent graders. When more than one grader is used, the results are averaged together.</p><doubt alpha="0.0" length="3" tooSmall="False" monospace="0.0">445</doubt></subsection><subsection number="6.2" title="Results"><p>Figure 4 shows the evaluation results for 16 un­seen Spanish dialogues containing 349 utterances translated into English. Acceptable is the sum of "Perfect" and "OK" sentences. For speech recog­nized input, we used the first-best hypotheses of the speech recognizer.</p><p>Two trends have been observed from this eval­uation as well as other evaluations that we have conducted. First, The GLR translation module performs better than the Phoenix module on tran­scribed input and produces a higher percentage of "Perfect" translations, thus confirming the GLR approach is more accurate. This also indicates that GLR performance should improve with bet­ter speech recognition and improved pre-parsing utterance segmentation. Second, the Phoenix module performs better than GLR on the first-best hypotheses from the speech recognizer, a re­sult of the Phoenix approach being more robust.</p><p>These results indicate that combining the two approaches has the potential to improve the trans­lation performance. Figure 5 shows the results of combining the two translation methods using the simple method described in the previous section. The GLR* parse quality judgement is used to de­termine whether to output the GLR translation or the Phoenix translation. The results were eval­uated only for in-domain sentences, since out-of-domain sentences are unlikely to benefit from this strategy. The combination of the two translation approaches resulted in a slight increase in the per­centage of acceptable translations on transcribed input (compared to both approaches separately). On speech recognized input, although the over­all percentage of acceptable translations does not improve, the percentage of "Perfect" translations was higher. <footnote anchor="2"/></p><footnote label="2">In a more recent evaluation, this combination method resulted in a 9.5% improvement in acceptable translations of speech recognized in-domain sentences. Although some variation between test sets is to be ex-</footnote></subsection></section><section number="7" title="Conclusions and Future Work"><p>In this paper we described the design of the two translation modules used in the JANUS system, outlined their strengths and weaknesses and de­scribed our efforts to combine the two approaches. A newly developed end-to-end evaluation proce­dure allows us to assess the overall performance of the system using each of the translations meth­ods separately or both combined.</p><p>Our evaluations have confirmed that the GLR approach provides more accurate translations, while the Phoenix approach is more robust. Com­bining the two approaches using the parse qual­ity judgement of the GLR* parser results in im­proved performance. We are currently investigat­ing other methods for combining the two transla­tion approaches. Since GLR* performs much bet­ter when long utterances are broken into sentences or sub-utterances which are parsed separately, we are looking into the possibility of using Phoenix to detect such boundaries. We are also develop­ing a parse quality heuristic for the Phoenix parser using statistical and other methods.</p><p>Another active research topic is the automatic detection of out-of-domain segments and utter­ances. Our experience has indicated that a large proportion of bad translations arise from the translation of small parsable fragments within out-of-domain phrases. Several approaches are under consideration. For the Phoenix parser, we have implemented a simple method that looks for small islands of parsed words among non-parsed words and rejects them. On a recent test set, we achieved a 33% detection rate of out-of-domain parses with no false alarms. Another approach we are pursuing is to use word salience measures to identify and reject out-of-domain segments.</p><p>We are also working on tightening the coupling of the speech recognition and translation modules of our system. We are developing lattice parsing versions of both the GLR* and Phoenix parsers, so that multiple speech hypotheses can be efficiently analyzed in parallel, in search of an interpretation that is most likely to be correct.</p></section><section title="Acknowledgements"><p>The work reported in this paper was funded in part by grants from ATR - Interpreting Telecom­munications Research Laboratories of Japan, the US Department of Defense, and the Verbmobil Project of the Federal Republic of Germany.</p><p>We would like to thank all members of the JANUS teams at the University of Karlsruhe and Carnegie Mellon University for their dedicated work on our many evaluations.</p><p>pected, this result strengthens our belief in the poten­tial of this approach.</p><doubt alpha="0.0" length="3" tooSmall="False" monospace="0.0">446</doubt><page local="6"/><p>In Domain (605 sentences)</p><doubt alpha="83.3" length="6" tooSmall="False" monospace="0.0">In Dom</doubt><p>Acceptable (Perfect 4- OK)</p><doubt alpha="0.0" length="4" tooSmall="False" monospace="0.0">86.2</doubt><doubt alpha="0.0" length="4" tooSmall="False" monospace="0.0">60.9</doubt><figure caption="Figure 5: September 1995 evaluation of GLR* combined with Phoenix. Cross-grading of 16 dialogues."></figure><doubt alpha="100.0" length="1" tooSmall="False" monospace="0.0">A</doubt><table caption="Figure 4: September 1995 evaluation of GLR* and Phoenix. Cross-grading of 16 dialogues." class="main" frame="box" rules="all" border="1" regular="False"><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p>(J LR*</p></td><td class="cell"><p>Phoenix</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p>transcriber!</p></td><td class="cell"><p>speech lst-best</p></td><td class="cell"><p>transcribed</p></td><td class="cell"><p>speech lst-best</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Perfect</p></td><td class="cell"><p>65/2</p></td><td class="cell"><p>34.7</p></td><td class="cell"><p>53.3</p></td><td class="cell"><p>35.5</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>ÔK</p></td><td class="cell"><p>18.8</p></td><td class="cell"><p>12.2</p></td><td class="cell"><p>25.3</p></td><td class="cell"><p>26.3</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Bad</p></td><td class="cell"><p>16.0</p></td><td class="cell"><p>29.2</p></td><td class="cell"><p>21.4</p></td><td class="cell"><p>17.1</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Recog Err</p></td><td class="cell"><p><b>+*</b></p></td><td class="cell"><p>23.9</p></td><td class="cell"><p><b>**</b></p></td><td class="cell"><p>21.1</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Out of Domain (485 sentences)</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Perfect</p></td><td class="cell"><p>58.5</p></td><td class="cell"><p>29.7</p></td><td class="cell"><p>44.2</p></td><td class="cell"><p>29.3</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>OK</p></td><td class="cell"><p>26.7</p></td><td class="cell"><p>42.4</p></td><td class="cell"><p>44.6</p></td><td class="cell"><p>41.1</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Bad</p></td><td class="cell"><p>14.8</p></td><td class="cell"><p>7.5</p></td><td class="cell"><p>11.2</p></td><td class="cell"><p>9.1</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Recog Err</p></td><td class="cell"><p>**</p></td><td class="cell"><p>20.4</p></td><td class="cell"><p>**</p></td><td class="cell"><p>20.5</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Acceptable (Perfect + OK)</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>In Dom</p></td><td class="cell"><p>84.0</p></td><td class="cell"><p>46.9</p></td><td class="cell"><p>78.6</p></td><td class="cell"><p>61.8</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Out of Dom</p></td><td class="cell"><p>85.2</p></td><td class="cell"><p>72.1</p></td><td class="cell"><p>88.8</p></td><td class="cell"><p>70.4</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>AU Dom</p></td><td class="cell"><p>84.5</p></td><td class="cell"><p>58.2</p></td><td class="cell"><p>82.9</p></td><td class="cell"><p>65.5</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr></table><table class="main" frame="box" rules="all" border="1" regular="False"><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p>GLR* with Phoenix</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>transcribed</p></td><td class="cell"><p>speech lst-best</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Perfect</p></td><td class="cell"><p>65.4</p></td><td class="cell"><p>39.7</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>OK</p></td><td class="cell"><p>20.8</p></td><td class="cell"><p>21.2</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Bad</p></td><td class="cell"><p>13.8</p></td><td class="cell"><p>15.2</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Recog Err</p></td><td class="cell"><p>**</p></td><td class="cell"><p>23.9</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr></table></section><references><p>D. Gates, A. Lavie, L. Levin, A. Waibel, M. Gavaldà, L. Maylield, M. Woszczyna and P. Zhan. <i>End-to-end Evaluation in JANUS: a Speech-to-speech Translation System, </i>To ap­pear in Proceedings of ECAf Workshop on Dia­logue Processing in Spoken Language Systems, Budapest, Hungary, August 1996.</p><p>. Lavie. An Integrated Heuristic Scheme for Partial Parse Evaluation, Proceedings of the 32nd Annual Meeting of the ACL (ACL-94), Las Cruces, New Mexico, June 1994.</p><p>Mayfield, M. Gavaldà, Y-H. Seo, B. Suhm, W. Ward, A. Waibel. "Parsing Real Input in JANUS: a Concept-Based Approach." In <i>Pro­ceedings of TMI 95.</i></p><p>. P. Rosé, B. Di Eugenio, L. S. Levin, and C. Van Ess-Dykema. Discourse processing of dialogues with multiple threads. In <i>Proceedings of AGL'95, Boston, MA, </i>1995.</p><p>M. Tomita. An Efficient Augmented Context-free Parsing Algorithm. <i>Computational Linguistics, </i>13(I-2):31-46, 1987.</p><p>M. Tomita. The Generalized LR Parser/Compiler - Version 8.4. In <i>Proceedings of Interna­tional Conference on Computational Linguis­tics (COLING'90), </i>pages 59-63, Helsinki, Fin­land, 1990.</p><p>M. Tomita and E. H. Nyberg 3rd. Genera­tion Kit and Transformation Kit, Version 3.2: User's Manual. Technical Report CMU-CMT-88-MEMO, Carnegie Mellon University, Pitts­burgh, PA, October 1988.</p><p>W. Ward. "Understanding Spontaneous Speech: the Phoenix System." fn <i>Proceedings of ICASSP-91, </i>1991.</p><p>W. Ward. "Extracting Information in Sponta­neous Speech." In <i>Proceedings of International Conference on Spoken Language, </i>1994.</p><p>M. Woszczyna, N. Aoki-Waibel, F. D. Buo, N. Coccaro, T. Horiguchi, K. and Kemp, A. Lavie, A. McNair, T. Polzin, L Rogina, C. P. Rosé, T. Schultz, B. Suhm, M. Tornita, and A. Waibel. JANUS-93: Towards Spontaneous Speech Translation. In <i>Proceedings of IEEE International Conference, on Acoustics, Speech and Signal Processing (ICASSP'94), </i>1994.</p><doubt alpha="0.0" length="3" tooSmall="False" monospace="0.0">447</doubt><p>. Lavie and M. Tomita. <i>GLR* - An Efficient</i> <i>Noise Skipping Parsing Algorithm for Context Free Grammars, </i>Proceedings of the third In­ternational Workshop on Parsing Technologies (IWPT-93), Tilburg, The Netherlands, August 1993.</p></references></body></article>