File Information
File: 05-lr/acl_arc_1_sum/cleansed_text/xml_by_section/relat/05/i05-2020_relat.xml
Size: 1,899 bytes
Last Modified: 2025-10-06 14:15:53
<?xml version="1.0" standalone="yes"?> <Paper uid="I05-2020"> <Title>Effect of Domain-Specific Corpus in Compositional Translation Estimation for Technical Terms</Title> <Section position="6" start_page="118" end_page="118" type="relat"> <SectionTitle> 6 Related Works </SectionTitle> <Paragraph position="0"> As a related work, (Fujii and Ishikawa, 2001) proposed a technique of compositional estimation of bilingual term correspondences for the purpose of cross-language information retrieval.</Paragraph> <Paragraph position="1"> In (Fujii and Ishikawa, 2001), a bilingual constituents lexicon is compiled from the translation pairs included in an existing bilingual lexicon in the same way as our proposed method. One of the major differences of the technique of (Fujii and Ishikawa, 2001) and the one proposed in this paper is that in (Fujii and Ishikawa, 2001), instead of the domain/topic specific corpus, they use a corpus of the collection of the technical papers, each of which is published by one of the 65 Japanese associations for various technical domains. Another important difference is that in (Fujii and Ishikawa, 2001), they evaluate only the performance of cross-language information retrieval but not that of translation estimation.</Paragraph> <Paragraph position="2"> (Cao and Li, 2002) proposed a method of compositional translation estimation for compounds.</Paragraph> <Paragraph position="3"> In the proposed method of (Cao and Li, 2002), translation candidates of a term are compositionally generated by concatenating the translation of the constituents of the term and are re-ranked by measuring contextual similarity against the source language term. One of the major differences of the technique of (Cao and Li, 2002) and the one proposed in this paper is that in (Cao and Li, 2002), they do not use the domain/topic specific corpus.</Paragraph> </Section> class="xml-element"></Paper>