Custom Machine Translation Management (Custom Glossary Model Details)

目次


    What is custom glossary setting/custom glossary model?

    The process of wrapping the standard model of MT learning service or the custom trained model registered in this system using a glossary to automatically output the translation defined in the glossary is called “Custom glossary setting” in this system (sometimes called "Glossary wrapping"). As the result of custom glossary setting, a custom glossary model is created. Once the custom glossary setting has been completed, the models set with glossaries can be used in Quick MT/PE of this system.

     Service 
    Usage Custom Glossary Model
    Quick MT Select in custom machine translation model list X
    Quick PE Select in custom machine translation model list X
    Language assets and custom MT models data registered during your LAC main contract period will be permanently deleted after a certain period of time after the contract period terminates. We recommend that you export your language assets data before the termination of your contract period. In addition, language assets and custom MT models data registered during your LAC trial period will be deleted immediately after the trial period terminates. Please note that data cannot be taken over in order to use in the LAC main contract period.

    Information in Custom Glossary Model Details screen

    Detailed data of the custom glossary model is displayed on this screen. You can only change the following items.

    • Custom Trained Model Name: An arbitrary string of each model. It is displayed in the following places. The default value is “Custom Glossary Model_YYYYMMDDhhmmss" whose end is the timestamp (JST) when the registration of the custom glossary model started. (Example: “Custom Glossary Model_20220201152040" if it starts at Feb 1, 2022, 15:40 JST)
      • Quick MT, Quick PE (Project Details screen):
        • MT engine "Google Translate": Options in the pull down list of Optional settings [Custom Trained Model]
        • MT engine "Kawamura NMT": Options in the pull down list of Required settings [General/Custom MT Model]
        • MT engine "Amazon Translate": Options in the pull down list of Optional settings [Custom Glossary Model]
    • Model Status: Specifies whether to be used in Quick MT/PE. The default value is “Enabled”. Set “Disabled” for a custom trained model that are not used in Quick MT/PE.
    • Comment: You can add any information about the custom glossary model.

    Also, at the bottom of the screen, the information on the language asset (glossary) used for the custom glossary setting is displayed.

    Model evaluation for custom glossary models

    On this screen, you can perform model evaluation of the custom glossary model. When you press the [Model Evaluation] button at the bottom of the screen, you can upload a bilingual file (which contains bilingual data of the source text and the correct translation, file format: xliff, csv, tsv, maximum 50,000 characters) for the model evaluation.

    As a result of the model evaluation, the following four indicators are calculated as numerical values, and you can see the changes before and after the glossary setting as follows. The first one is the value from the standard model (generic model) (*) of the MT learning service used for the glossary setting, and the last one is the value from the custom glossary model. When a custom trained model was used for the glossary setting, the second value will be displayed which from the custom trained model. If the value of BLUE, NIST, and RIBES changes higher, and the value of WER changes lower, it can be interpreted that an effective customization has been implemented by the custom training. You can also check the detailed meaning of each indicator in this blog post.

    • BLEU
    • NIST
    • RIBES
    • WER

     

    ModelEval2_ja

     

    For the model evaluation, it is recommended to use a bilingual file whose source text is similar to the sentence you want to translate using the custom trained model. This allows you to know “how effectively you can translate the sentences you actually want to translate” in numerical terms.
    Only UTF-8 is supported for the character code of the bilingual file for the model evaluation.
    *About the standard model used for the evaluation: If the used MT learning service is "Kawamura NMT", the standard model of the type selected when registering the custom glossary model (General NT, Patents NT, Finance Services, Finance NT (IR/Disclosure), Legal documents NT) will be used.

    Duplicate terms in the glossary

    You can register duplicate terms (bilingual data) in the glossary, but it is recommended that a term pair (source-target text) be unique, whether referenced as a glossary or incorporated into a custom glossary model. However, there are cases where you want to change the translation of each term and the translation of a compound word, as shown below.

     English 
     Japanese 
    asset 資産
    management 管理
    asset management アセットマネジメント
    If you create a custom glossary model with a glossary which includes such bilingual data, when you machine translate the source text (in this case, English) using the model, the term with the longer source length will be prioritized and the translation will be adopted. In the above example, if “asset management” appears in the source text, “アセットマネジメント” will be prioritized as the translation, so this source text will not be output as “資産管理”.

     

    This system assumes that glossary includes terms that do not change much in context, such as technical terms, product names, and proper nouns. For example, when creating an English-Japanese glossary, you can unify the translations by registering two source sentences (terms), singular and plural, as separate records. However, in the case of a Japanese-English glossary that is in the opposite direction, even if you register two translation records for one source, it will not be automatically used properly in machine translation. It can be said that terms whose singular/plural form changes depending on the context should not be registered in the glossary.