<?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>Machine Translation by Case Generalization</title><author surname="Nomiyama" givenname="Hiroshi"><org  name="IBM Research Tokyo" country="Japan" city="Tokyo"/></author></firstpageheader><frontmatter><p>Machine Translation by Case Generalization</p><p><b>Hiroshi Nomiyama</b></p><p><b>IBM Research, Tokyo Research Laboratory 5-19 Sanbancho, Chiyoda-ku,Tokyo 102 Japan E-Mail:</b>nomiyama@trl.vnet.ibm.com</p></frontmatter><abstract>Case-based machine translation is a promising ap­proach to resolving problems in rule-based machine translation systems, such as difficulties in control of rules and low adaptability to specific domains. We pro­pose a new mechanism for case-based machine trans­lation, in which a large set of cases is generalized into a smaller set of cases by using a thesaurus. </abstract></header><body><section number="1" title="Introduction"><p>Case-Based/Example-Based Machine Translation (CBMT/EBMT) has been proposed as a way of over­coming the knowledge acquisition bottleneck in ma­chine translation. This approach is based on the simple concept of translating sentences by analogy with simi­lar cases stored in a set of casesfa case-base) [1, 2, 3, <b>4].</b></p><p>This approach has two advantages in terms of knowl­edge acquisition. CBMT/EBMT ensures that (1) if the same case as the input exists in the case-base, then the same result will be obtained, and (2) if a similar case exists in the case-base, then a similar result will be ob­tained. In the first instance, which cases are regarded as the same depends on the equality metrics of the sys­tem. In the second instance, which cases are regarded as similar depends on the similarity metrics. Rule de­velopers or users can control the system on the basis of equality and similarity without understanding the global flow of controls.</p><p>In applying this idea to practical machine transla­tion systems, there are still two serious problems. One is that CBMT/EBMT requires a great deal of compu­tation because of its inherent need to retrieve a huge number of cases and calculate their similarities to the input. For practical systems, several hundreds of thou­sands of cases must be accessible.</p><p>CBMT/EBMT systems should not impose any restrictions on cases to be added to the case-base in an effort to keep the case-base small, since the similarity metrics depends on the frequencies of cases. If cases are restricted, sufficient information to control the rules is not acquired.</p><p>The other problem of CBMT/EBMT is the diffi­culty of defining a semantic distance. Though the­sauri are used as bases for semantic distance calcula­tion in CBMT/EBMT, it may be impossible to define a general semantic distance by using thesauri alone. Semantic distances between words are defined accord­ing to which specific words are related to their trans­lations. For example, in translating the word w^t^ ■£&gt;"(eat,feed,. ..), "^t(dog)-^î-Ê^'&amp;"is equivalent to "a dog eats," <b>"4<footnote anchor="1"/> </b>(cow)-7&amp;î-jiû^£" is equivalent to "a cow feeds," and ( horse)-<b>^&gt;Vft</b>'^&lt;5" is equiva­lent to "a horse feeds." In these cases, "^"(cow) is closer to "$§" (horse) than "^"(dog), because differ­ent words are selected for each translation of £" with "^"(cow) and ll^t"(dog). But in translating "7Ë&amp;,,(run1gallop,. .. ), <b><i>(dog)-ffî-y&amp;&amp;n </i></b>is equiva­lent to "a dog runs," <b>"4-<footnote anchor="1"/> </b>(cowJ-^-jÊS" is equivalent to "a cow runs," and <b><i>"M </i></b>(horseJ-^-TË-îi" is equivalent to "a horse gallops." In these cases, <b>"4-" </b>(cow) is closer to "Ü"(dog) than ".^"(horse).</p><p>If such incomplete semantic distances calculated by thesauri alone are used for CBMT/EBMT, excep­tional cases may be interpreted as general ones(over-generalization). Over-generalization is a major prob­lem in translating idiomatic expressions. For exam­ple, <b><i>"M </i></b>(head)-#*-#Jft£&gt;" has two translations: "hurt one's head " or, idiomatically, "be smart." But "Hoß (head)-^î-^îJii'îi" has only one interpretation, "hurt one's head," though the word "<b>ISpÜ</b>" has almost the same meaning as "M".</p><p>It is obvious that <b><i>uW.M</i></b><b><i>-&amp;-tytl2&gt;" </i></b>can be trans­lated correctly by adding this translation pair into the case-base. The addition, however, cannot prevent the idiomatic expression <b><i>"UR-ffi-tyilZ)" </i></b>from being in­terpreted generally.<page local="2"/> The idiomatic interpretation still may be adopted for "X-^-^Jft^" if X is more simi­lar to the word "jîjl" than the words in the case-base whose pattern is "X-^-^OttS."</p><doubt alpha="46.7" length="92" tooSmall="False" monospace="0.0">Acresde COUNG-92, Nantes, 23-28 août 1992 7 1 4 Proc. of COLING-92, Nantes, Aug. 23-28, 1992</doubt><p>Sato <b>[3] </b>and Sumita <b>[4] </b>weigh each slot depending on how much it affects the translation. However, since such weights are calculated only for each slot, the over-generalization that occurs inside of a slot is not re­solved. To avoid over-generalization, we need some mechanism to encapsulate exceptions rather than to adjust the semantic distance.</p></section><section number="2" title="Machine Translation by Case Generalization"><p>A case-base, in contrast to a set of rules, has inherent redundancy, because cases are collected without pre­selection. In the simplest case, if the sentence "A" has only one translation equivalent "a,"  then the single</p><doubt alpha="60.5" length="43" tooSmall="False" monospace="0.0">case "A" —* "a" is enough to translate "A."</doubt><p>But if we view the case-base as a collection of sen­tences, the same sentences rarely seem to occur *. Sen­tences can, however, be divided into smaller fragments which are meaningful units for translation according to the some linguistic models, which we call translation patterns.</p><p>These fragments are combined for use in translating sentences. Fragments divided on the basis of trans­lation patterns are obviously more effective than sen­tences, because smaller fragments are more likely to match than full sentences.</p><p>We generalize such fragments extracted according to each translation pattern, using a thesaurus, by re­placing the words that occur in cases by more general concepts in the thesaurus. The words to be replaced are determined by their frequencies in the case-base. Frequent occurring fragments should be assigned more weight than less frequent by occurring fragments. The frequencies of fragments are used to weigh generalized cases in generalization.</p><p>Semantic distances are calculated for each transla­tion pattern as the importances of generalized cases. Only meaningful categories for the translation pattern are stored as generalized cases, except that the most meaningful category is taken as a default. For example,</p><p><b>lThe case-base should contain natural sentences rather than examples which are only the smallest fragments effective for translation. We distinguish CBMT from EBMT in accordance with this viewpoint.</b></p><p>the word u^C"(dog) may be generalized into the con­cept &lt;dog&gt; <footnote anchor="2"/> for translation of "tS| (. "("a dog barks"), whereas it may be replaced by the more general con­cept &lt;animal&gt;, for other translation patterns in which the concept &lt;dog&gt; is not meaningful-While generalizing cases, we can identify exceptional cases as those which cannot be generalized. Once we identify exceptions, then w« can prevent such excep­tions from being interpreted generally.</p><p>In this way, cases are generalized according to the translation pattern into generalized cases with con­cepts as the values of their variables.</p><p>In addition to generalized cases, rules can be formu­lated according to translation patterns. Generalized cases and manually written rules are assumed to be the same as objects in CBMT. It is valuable to have rules available as well as cases, especially when the case-base contains insufficient cases. If rules are not available, there must be sufficient cases from the time the system is first used. Incremental development of any domain is possible only if general rules are avail­able.</p><p>In accordance with these basic ideas, we propose a method of machine translation in which cases are gen­eralized. In our approach, we define linguistic patterns in translation. According to these patterns, the cases in the case-base are divided into smaller fragments and are generalized. Both rules and generalized cases are used to translate sentences.</p><p>CBMT is divided into two sub-processes: (1) best matching, to search for the most similar cases in the case-base, and (2) application control, to control the combination of similar cases for translation. Applica­tion control is a general problem in machine transla­tion, whereas best matching is a problem unique to CBMT. If the best matching process returns certainty factors, the system is controlled using these factors on the basis of the some other model such as Watanabe's [5].</p><p>In this paper, we concentrate on best matching using a thesaurus.</p><p><b>^Concepts are enclosed between arrowheads (&lt; and &gt;) in this paper.</b></p><doubt alpha="47.3" length="93" tooSmall="False" monospace="0.0">Acresde COUNG-92, Naotes, 23-28 août 1992 7 1 5 Proc. of COLING-92. Nanttes, Aug. 23-28, 1992</doubt><page local="3"/></section><section number="3" title="Generalizing Cases"><subsection number="3.1" title="Division   and   Linearization of Cases"><p>At first, we define a translation pattern <b><i>(TPf) </i></b>as fol­lows.</p><doubt alpha="55.6" length="18" tooSmall="False" monospace="0.0">TPi = [Pm,V„Pt,Vt]</doubt><p><b><i>P, : </i></b>Structural Pattern in Source Language (SL) <b><i>Vt </i></b>: List of Lexical Variables in SL <b><i>Pt </i></b>: Transformation into Target Language (TL) V( : List of Variables in TL</p><p>We call the number of variables in <b><i>VM </i></b>the term num­ber <b><i>(M;) </i></b>of <b><i>TP,.</i></b></p><p>Next, we extract translation pattern cases <b><i>(TPCt) </i></b>from the case-base by applying the pattern matches described in TP, to all cases in the case-base.</p><doubt alpha="50.0" length="14" tooSmall="False" monospace="0.0">TPd = {L„C„Lt]</doubt><p><b><i>L, : </i></b>List of Values of Lexical Variables in SL <b><i>Ct </i></b>: List of Constraints in SL <b><i>Lt </i></b>: List of Values of Variables in TL</p><p>If some patterns other than those specified in <b><i>Pa </i></b>are related in translation, those patterns are described in constraints (Cf).</p><p>These TPC,s are linearlized into linearlized transla­tion pattern cases <b><i>(LTPCi).</i></b></p><doubt alpha="52.6" length="19" tooSmall="False" monospace="0.0">LTPCi : Lt—» (C„Lt)</doubt><p>We call the right-hand part of <b><i>LTPCi </i></b>the value (V). The examples in Fig. 1 are extracted <b><i>LTPds </i></b>in Japanese-to-English translations of "NOUN ni VERB," where we assume a translation pattern in which an English preposition is determined by a bi­nary relation of a Japanese noun and a Japanese verb.</p><p>In the following section, we show how to general­ize <b><i>LTPCiS </i></b>into generalized linear translation pattern cases <b><i>(GLTPCi) </i></b>by replacing words with more gen­eral concepts in the thesaurus, and calculate degrees of importance for them.</p><doubt alpha="54.0" length="50" tooSmall="False" monospace="0.0">["Sangatu"(March) ,"Kowasu"(destroy) ] -*([],["in"</doubt><doubt alpha="53.7" length="54" tooSmall="False" monospace="0.0">["Sigatu"(April) ,"Girr&gt;nsnru"{discuss) ] "*"([],["in"</doubt><doubt alpha="53.1" length="49" tooSmall="False" monospace="0.0">["Gogatu"(May) ,"Saiketusuru"(vote) ] -*([],["in"</doubt><doubt alpha="52.2" length="46" tooSmall="False" monospace="0.0">["Rokugatu"(June) ,"Hieru"(cool) ] -*([j,["in"</doubt><doubt alpha="48.9" length="47" tooSmall="False" monospace="0.0">["Getuyou"(Monday) ,"Arau"(wash) ] ""*([],["on"</doubt><doubt alpha="52.0" length="50" tooSmall="False" monospace="0.0">["Kayou" (Tuesday) ,"Kimaru"(decide) ] -*([],["on"</doubt><doubt alpha="51.9" length="52" tooSmall="False" monospace="0.0">["Syuumatu" (weekend),"Agaru" (raise) ] ~* ([],["on"</doubt><doubt alpha="47.7" length="44" tooSmall="False" monospace="0.0">["Higasi"(east) ,"Uturu"(move) ] "*([],["to"</doubt><doubt alpha="54.2" length="48" tooSmall="False" monospace="0.0">["Toukyou"(Tokyo) ,"Idousuru"(move) ]—"([],["to"</doubt><doubt alpha="54.9" length="51" tooSmall="False" monospace="0.0">["Sitigatir'(July) ,"Idousuru"(move)]     ([j,["in"</doubt><figure caption='Figure 1: Translations of "NOUN ni VERB"'></figure></subsection><subsection number="3.2" title="Case Generalization by Means of"><p>a Thesaurus 3.2.1   Creation of N-Term Partial Thesauri</p><p>We create working thesauri, <b><i>PTHi(j) </i></b>(1 &lt; <b><i>j &lt; Mi), </i></b>for each term. They include every word in the j-th term, and set pairs of values and their frequencies in each word node.</p><p>Here we define the importances used to weigh gen­eralized cases.</p><p>Importance of a Link <b><i>(IL) </i></b>The importance of a Unk <b><i>(IL) </i></b>is the probability of occurrence of cases that occurred in the subtree of <b><i>PTHt(j). IL </i></b>is defined as follows.</p><doubt alpha="0.0" length="3" tooSmall="False" monospace="0.0">"■5</doubt><p>where <b><i>S </i></b>is the total number of cases in the subtree connected with the link, and C, is the total number of <b><i>LPTds </i></b>extracted from the case-base according to <b><i>TPi.</i></b></p><p>Importance of a Node <b><i>(IN) </i></b>The importance of a node <b><i>(IN) </i></b>shows the degree of variance of values in a subtree. <b><i>IN </i></b>is defined as follows.</p><p>where is the probability of each value in the sub­tree <footnote anchor="3"/>.</p><p>Importance of a Value (/V) The importance of a value L (/V) in the node k is defined as follows.</p><p>If node k ia a word node, then <b><i>IVki </i></b>= frequency of value L in node k where m is a node linked to node <b><i>k, </i></b>and <b><i>IVmi </i></b>is the importance of value <b><i>L </i></b>in node <b><i>m.</i></b><page local="4" global="1992"/><b><i></i></b></p><footnote label="3">We adopt the same expression as that used by Stanfill [6] and Sumita [4].</footnote><doubt alpha="46.8" length="94" tooSmall="False" monospace="0.0">Actes de COLING-92. Nantes, 23-28 août 1992 7 1 6 Proc. of COLING-92, Nantes. Aug. 23-28, 1992</doubt><doubt alpha="100.0" length="4" tooSmall="False" monospace="0.0">else</doubt><p>Importance of a Generalized Case <b><i>(IC) </i></b>The im­portance of a <b><i>GLTPCi (IC) </i></b>is defined as follows.</p><p>where <b><i>IVji </i></b>is the importance of value <b><i>L, </i></b>which is the same as the value of the <b><i>GLTPCi-</i></b></p><subsubsection number="3.2.2" title="Subdivision of Conceptual Leaf Nodes"><p>According to the definitions given in the previous section, at first <b><i>I La </i></b>and <b><i>INa </i></b>are set in all the links and nodes in <b><i>PTHj(j), </i></b>and <b><i>IVs </i></b>are calculated in con­ceptual leaf nodes in <b><i>PTHi(j).</i></b></p><p>If <b><i>IV </i></b>is not the maximum value in a conceptual leaf node and is greater than the pre-defined thresh­old value and its frequency is greater than 2, the node is subdivided into more specific concepts.</p><p>Subdivision occurs because a specific category which doesn't exist in the thesaurus is effective for a specific translation pattern. Only the difference from the the­saurus is kept as the translation pattern thesaurus i <b><i>(TPTHi).</i></b></p></subsubsection><subsubsection number="3.2.3" title="Propagation of Importance of Values"><p>Next, we calculate <b><i>IV </i></b>in all nodes other than con­ceptual leaf nodes by propagating <b><i>IV. </i></b>The propaga­tion is done by multiplying the importances of values by the importances of links, and the sum of all the propagated values is multiplied by the importance of the node. At first, the propagation is done upward, starting from the conceptual leaf nodes. During up­ward propagation, downward propagation is done if a child node is a conceptual node and a propagated value is greater than the maximum importance of values in the child node. Downward propagation prevents over-generalization.</p><p>We show examples of results of importance calcu­lation in Fig. 2 and Fig. 3, for the first and sec­ond terms respectively. In Fig. 2, the subdivision oc­curred in the node &lt;Time&gt; and the new node &lt;*X*&gt; was created. A downward propagation occurred in the node &lt;Concrete&gt; in Fig. 2. The word "in" was made more important than the word "to" in the node &lt;Concrete&gt;.</p><doubt alpha="38.8" length="338" tooSmall="False" monospace="0.0">[&lt;&gt;,&lt;Destruction&gt;] — ([],["in"]) [&lt;&gt;,&lt;Speech&gt;] - ([]1["in,,l)[&lt;&gt;,"Saiketu3uru"(decide)j -*• ([],["in"]) [&lt;&gt;,&lt;&gt;!-([],["in"]) [&lt;*X*&gt;,&lt;Action&gt;]-*([],[aon"]) [&lt;*X*&gt;,"Kimaru"(decide)] — ([],["on"]) [&lt;*X*&gt;,&lt;Up-Down&gt;] -* ([],[ W]) [&lt;Location&gt;,&lt;Abstract&gt;]~*((],("to"l) [&lt;Direction&gt;,&lt;Abstract&gt;] — ([],["to"]) [&lt;&gt;,l(Idousuru"(movc)] —+ ([],[kito"])</doubt><p>Figure 4; Result of the Intra-Term Generalization</p></subsubsection><subsubsection number="3.2.4" title="Intra-Term Generalization of LTPC,"><p>According to importances calculated according to the method described in the previous section, <b><i>LTPCi» </i></b>are generalized in the j-th term. If the value with the highest <b><i>IV </i></b>in the child node is the same as the value with the highest <b><i>IV </i></b>in the parent node, then the word in the term is generalized by the concept in the parent node. This process of generalization is repeated un­til no further generalization is possible, and only the most generalized cases are kept. If identical cases are obtained as a result, only one case is kept.</p><p>We show an example of intra-term generalization of ["Kayou" (Tuesday ),"Kimaru" (decide)] —*■ ([],[4ion"]). Initially, the firts term "Kayou''(Tuesday) is gener­alized. The value of this case ([],[l'ou"]) is the same as the value with the highest <b><i>IV </i></b>in the parent node &lt;*X*&gt; (see Fig. 2), so "Kayou"(Tuesday) is re­placed by &lt;*X*&gt;. The value ([],["on"]) is not the value with the highest <b><i>IV </i></b>in the parent node of &lt;*X*&gt;, and therefore generalization stops at the first term. Next, the second term "Kimaru"(decide) is generalized. In the parent node &lt;Decision&gt; of "Ki-maru"(decide), the value that is the same as the value of the case is one of the values with the highest <b><i>IV. </i></b>Consequently, parent nodes are checked to de­termine which value is more important. In the root node, ([],["on"]) is less important than ([],["in"]), so no generalization occurs for the second term. Fi­nally, [&lt;*X*&gt;,"Kirnaru"(decide)]-"([],["on"]) is ob­tained as the result of intra-term generalization.</p><p>The result of intra-term generalization for all the <b><i>LTPCts </i></b>in Fig. 1 is shown in Fig. 4.</p></subsubsection><subsubsection number="3.2.5" title="Inter-Term Generalization of LTPCi"><p>Next we generalize cases over terms. Inter-term gen­eralization takes <b><i>ICs </i></b>into consideration.  If <b><i>Mi </i></b>= 1,<page local="5" global="1993"/></p><doubt alpha="58.2" length="79" tooSmall="False" monospace="0.0">MRoliug«uM,(Q,rin"J)Ma*tuyou",1,{n,ron'']) "SMgatuM .(D.rinl)"KijrouM,(n.["«r])</doubt><doubt alpha="55.0" length="40" tooSmall="False" monospace="0.0">-8»flfl«tu"1i,(D,n^)"Syuumatu-.HD.ron"))</doubt><figure caption="Figure 2: First-Term Partial Thesaurus"></figure><p>Figure <b>3: </b>Second-Term Partial Thesaurus then the result of intra-term generalization with <b><i>ICs </i></b>is the generalized linear translation pattern case i <b><i>(GLTPCi).</i></b><page local="6" global="1994"/><b><i> </i></b>H Afj &gt; 1, j-th term maximum gener­alization <b>(1 &lt; </b><b><i>j &lt; Mi) </i></b>is done for each term. In j-th term maximum generalization, terms other than the j-th term are fixed first and the j-th term is general­ized as much as possible. Then, the maximum possible generalization is done for remaining of terms in turn. If <b><i>Mi </i></b>&gt; 1, then <b><i>Mi </i></b>x <b><i>(M, </i></b>~ 1) <b><i>GLPTQs </i></b>are obtained. If identical cases are obtained as a result, only one case is kept.</p><doubt alpha="47.3" length="93" tooSmall="False" monospace="0.0">Actes de COLING-92. Nantes, 23-28 août 1992 7 1 8 Proc. of COLING-92. Nantes, Aug. 23-28,1992</doubt><p>We show an example of inter-term generalization of [&lt;DirectioiL&gt;,&lt;Abstract&gt;] ([J,["to"]). Initially, first-term maximum generalization is done. <b><i>IVs </i></b>in the node &lt;Abstract&gt; are shown below (sen PT/f,-(2) in Fig. 3).</p><doubt alpha="14.3" length="56" tooSmall="False" monospace="0.0">(D,["to"J) : 0.027 (0,["in"]) : 0.020 (0,["on"]) : 0.006</doubt><p><b><i>IVa </i></b>in the node &lt;Abstract&gt;, which is the parent node of &lt;Direction&gt;, are shown below (see PTi/,(l) in Fig. 2).</p><doubt alpha="10.2" length="59" tooSmall="False" monospace="0.0">([],["in»]) : 0.192 (|],("on"]) : 0.035 ([],("to»]) : 0.007</doubt><p>Their totals are as follows.</p><doubt alpha="6.6" length="106" tooSmall="False" monospace="0.0">([),["to"]) : 0.027 + 0.007 - 0.034 ([|,["in"]) : 0.020 + 0.192 = 0.212([j,["on"]) : 0.006 + 0.035 - 0.041</doubt><p>Since ([(.["to"]) doesn't have the highest importance, the case is not generalized any further in the first term.</p><p>Next, the second term is generalized. The <b><i>IVs </i></b>in the node &lt;Direction&gt; are shown below (see Fig. 2).</p><doubt alpha="20.0" length="15" tooSmall="False" monospace="0.0">(0,["to"D : 0.1</doubt><p><b><i>IVs </i></b>in the node &lt;&gt;, which is the parent node of &lt;Abstract&gt;, are shown below (see Fig. 3).</p><doubt alpha="13.2" length="53" tooSmall="False" monospace="0.0">(ö,["in"]) : 0.011 (0,("to"]) : 0.008 (Ö,[W]) : 0.006</doubt><doubt alpha="41.7" length="12" tooSmall="False" monospace="0.0">[&lt;&gt;ï&lt;&gt;)o.iis</doubt><doubt alpha="31.0" length="142" tooSmall="False" monospace="0.0">[&lt;*X*&gt;,&lt;&gt;] -([mw])0.306 [&lt;Concrete&gt;,&lt;Abstract&gt;] -+ ([],[l'to"]) 0.037 [&lt;Location&gt;,&lt;&gt;] — ([],[uto"]) 0.108 [&lt;Direction&gt;,&lt;&gt;] — ([],["to"|) 0.108</doubt><figure caption="Figure 5: Result of the Inter-Term Generalization"></figure><doubt alpha="7.1" length="98" tooSmall="False" monospace="0.0">(|],["to"]) : 0.1 + 0.008 - 0.108 ({],['ïn"]) : 0 -I- 0.011 - 0.011 ((],[W]) : 0 -t- 0.006 - 0.006</doubt><p>Since ([],[LLto"]) has the highest importance, the sec­ond term is generalized into the root node &lt;&gt;, and the general­ization stops because there are no more parent nodes. Therefore [&lt;Direction&gt;,&lt;&gt;] — ([],[';to"]) 0.108 is the result of first-term maximum generalization of [&lt;Direction&gt;,&lt;Abstract&gt;] ([],[k'to;']).</p><p>The result of inter-term generalization for all the <b><i>LTCPiS </i></b>in Fig. 1 is shown in Fig. 5.</p></subsubsection><subsubsection number="3.2.6" title="Addition of Translation Rules"><p>Finally, translation rules (T/c\s) are added to the set of <b><i>GLTPC</i></b><i>'iH, </i><b><i>TR,a </i></b>are descriptions in which concepts are specified as the values of variables of <b><i>L„ </i></b>of <b><i>LTPCiS. </i></b>If the same case already exists in the set of <b><i>GLTPC,, </i></b>then it is not added. If only the value of the case is different from <b><i>TRi, </i></b>then it is replaced by <b><i>TR,. </i></b>Other­wise, <b><i>TRi </i></b>is added with its <b><i>IC. </i></b>The <b><i>ICs </i></b>for <b><i>TRiS </i></b>are calculated in the same way as for <b><i>GLTPC,s.</i></b></p></subsubsection></subsection></section><section number="4" title="Best-Matching Algorithm"><p>The XP;s, the set of <b><i>GLTPCi </i></b>the <b><i>TPH.s, </i></b>and the thesaurus are used in best matching. The values of variables in <b><i>Va </i></b>are extracted from the input sentence by applying pattern matching according to the description of TP, . The best-matching process retrieves the most similar case from the set of <b><i>GLTPC,.</i></b></p><p>If <b><i>Mi — </i></b>1, words which are equivalent to the word that is a value of the variable in <b><i>Va </i></b>are first searched for in the value of the corresponding variable in <b><i>Lt</i></b>of <b><i>GLTPCiS. </i></b>If none are found, upper concepts re­trieved in either <b><i>TPTHi </i></b>or the thesaurus are searched in turn. The <b><i>GLTPCi </i></b>which is found first is the shortest-distance <b><i>GLTPCi (SDGLTPQ). </i></b>If C. in <b><i>GLTPCi </i></b>is not null, then it is also evaluated, whether it is true or false.</p><page local="7" global="1995"/><p>If <b><i>Mi &gt; </i></b>1, the j-th term shortest-distance <b><i>GLTPC,s (SDGLTPCj) </i></b>of each term are searched for. If <b><i>Mi = </i></b>2, <b><i>SDGLTPCj </i></b>holds the shortest-distance word or concept in the first term, and <b><i>SDGLTPCj </i></b>holds the shortest-distance word or concept in the second term. If <b><i>M, &gt; </i></b>1, <b><i>(Mi </i></b>~ 1) <b><i>SDLTPCjH </i></b>are obtained for each j-th term. A total of <b><i>M, </i></b>x <b><i>(M{ </i></b>-1) <b><i>SDLTPCjS&amp;w </i></b>ob­tained. The <b><i>SDGLTPCj </i></b>with the highest importance is selected as the <b><i>SDGLTPC.</i></b></p><p>We will show an example in retrieving the most sim­ilar example for "Getuyou(Monday)ni-Huru(rain)." Suppose the parent node of "Hum" is &lt;CHmate&gt;. At first, <b><i>SDGLTPCx </i></b>will be searched for in <b><i>GLTPCts </i></b>(see Fig. 5). "Getuyou" does not exist in any first terms in the set of <b><i>G LTP da. </i></b>Therfore &lt;*X*&gt; which is the parent node of "Getuyou" is searched for and (&lt;*X*&gt;,&lt;&gt;1 — (Q,["on"]) 0.306 is found. The sec­ond term of this <b><i>GLTPCi </i></b>is a upper concept of "Hum," so this is <b><i>SDGLTPCi. </i></b>Next, <b><i>SDGLTPC2</i></b>is searched for and is found to be the same as <b><i>SDGTPC-i. </i></b>Consequently, the most similar <b><i>GLTPCi </i></b>is [&lt;*X*&gt;,&lt;&gt;] — ([],["on"]) 0.306, and the word "on" is set as a preposition.</p></section><section number="5" title="Discussion"><p>In the CBMT approach, the linguistic model, which is a set of translation patterns, is important both for the compaction ratio of a case-base and for similar­ity metrics. If the model is not appropriate, most cases remains ungeneralized, and unnatural cases are retrieved as similar cases to the input. The problems of constructing linguistic models are the same as in rule-based systems.</p><p>However, our approach assumes that the linguistic model does not include controls of rules and general­ized cases. Whether or not this assumption is correct, it is very difficult to define controls in such a way that any exceptional cases are encapsulated properly. Our approach provides an engineering solution to these dif­ficulties.</p><p>In our approach, the quality of translations depends on the quantity of cases rather than the quality of the thesaurus. Therefore, it is important to explore (semi-)automatic case acquisition from bilingual cor­pora,</p><p>To construct a huge case-base is easier than to con­struct a well-defined thesaurus, because cases are con­structed locally without taking account of side-effects. To define an effective thesaurus for translation, every effective category for translation must be included, and every intermediate category that is effective for trans­lation must be included in order to calculate semantic distances properly.</p><p>If, on the other hand, thesauri can be developed in­dependently from the case-base, developers or users can select the most appropriate thesaurus for the do­main.</p></section><section number="6" title="Concluding Remarks"><p>This paper has described <b>a </b>framework for a machine translation using a mixture of rules and cases general­ized by means of <b>a </b>thesaurus, which is much smaller than the case-base itself. Since the importances of rules and generalized cases are calculated in advance by gen­eralization, it is not necessary to calculate them during the best-matching, which is done by exact matching of words or upper concepts in the thesaurus.</p></section><section title="Acknowledgements"><p>I would like to thank Masayuki Morohashi and the members of Japanese Processing Group of Tokyo Re­search Laboratory, IBM Japan, for their valuable sug­gestions and encouragement, and Michael McDonald for his helpful advice on the wording of this paper.</p></section><references><p>(1| Nagao, M., "A Framework of a Mechanical Transla­tion between Japanese and English by Analogy Princi­ple," Elithorn, A. and Banerji, R. (eds.): <i>Artificial and Human Intelligence, </i>NATO, 1984.</p><p>[2] Sadler, V., "Working with Analogical Semantics: Dis­ambiguation Techniques in DLT," FORIS Publications, 1989.</p><p>[3] Sato, S., and Nagao, M., "Toward Memory-based Translation," Proc. of Coling '90.</p><p>[4] Sumita, E., Iida, IL, and Kohyama, IL, "Translating with Examples: A New Approach to Machine Transla­tion," Proc. of the 3rd Int. Conf. on Theoretical and Methodological Issues in Machine Translation of Natu­ral Languages, 1990.</p><p>[5j Watanabe, H., "A Similarity-Driven Transfer System," Proc. of Coling '92.</p><p>[6] Stanfill, C. and Waltz, D„ "Toward Memory-Based Reasoning," Comm. of ACM, Vol.29, No.12, pp. 1213­1228, 1986.</p></references></body></article>