[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-18。"],[[["\u003cp\u003eFuzzy matching in entity recognition allows for flexible matching of multi-word values and synonyms, where the word order does not impact the match, unlike exact matching.\u003c/p\u003e\n"],["\u003cp\u003eEnabling fuzzy matching simplifies entity definition by eliminating the need to define every permutation of multi-word entity values or synonyms, allowing you to specify fewer examples.\u003c/p\u003e\n"],["\u003cp\u003eFuzzy matching can be enabled in the Dialogflow ES console by checking the "Fuzzy matching" option when creating or editing an entity.\u003c/p\u003e\n"],["\u003cp\u003eFuzzy matching should not be used for entities that require strict matching, such as IDs or identification numbers, and it is not compatible with regexp entities.\u003c/p\u003e\n"],["\u003cp\u003eFuzzy matching may also result in partial matches and spell corrections, matching end-user inputs to the closest synonym, even if not an exact match.\u003c/p\u003e\n"]]],[],null,["# Fuzzy matching\n\nBy default, entity matching requires an exact match for one of the entity entries.\nThis works well for single-word entity entry values and synonyms\nbut may present a problem for multi-word values and synonyms.\nFor example,\nconsider a *ball* entity\nthat should be matched for the following end-user expression parts:\n\n- \"ball\"\n- \"red ball\"\n- \"ball red\"\n- \"small ball\"\n- \"ball small\"\n- \"small red ball\"\n- \"small ball red\"\n- \"red small ball\"\n- \"red ball small\"\n- \"ball small red\"\n- \"ball red small\"\n\nFor a match to occur,\nyou normally need to define an entity entry value and synonyms for each of these permutations.\nHowever, with fuzzy matching enabled,\nthe ordering of the words in a value or synonym does not matter.\nThe following will trigger a match for all of the examples above:\n\n- \"ball\"\n- \"red ball\"\n- \"small ball\"\n- \"small red ball\"\n\nWhere to find this data\n-----------------------\n\nWhen building an agent,\nit is most common to use the\nDialogflow ES console ([visit documentation](/dialogflow/docs/console), [open console](https://dialogflow.cloud.google.com)).\nThe instructions below focus on using the console.\nTo access entity data:\n\n1. Go to the [Dialogflow ES console](https://dialogflow.cloud.google.com).\n2. Select an agent.\n3. Select **Entities** in the left sidebar menu.\n\nIf you are building an agent using the API instead of the console, see the\n[EntityTypes reference](/dialogflow/docs/reference/common-types#entitytypes).\nThe API field names are similar to the console field names.\nThe instructions below highlight any important differences between the console and the API.\n\nCreate a fuzzy matching entity\n------------------------------\n\nTo create a fuzzy matching entity:\n\n1. Open an existing entity or create a new one.\n2. Check **Fuzzy matching**.\n3. Enter one or more entries in the table.\n4. Click **Save**.\n\nIf you are using the API to create or update entities,\nset the `enable_fuzzy_extraction` field to true for the `EntityType`.\n\nLimitations\n-----------\n\nThe following limitations apply:\n\n- Fuzzy matching cannot be enabled for [regexp entities](/dialogflow/docs/entities-regexp). These features are mutually exclusive.\n- Fuzzy matching should not be enabled for entities which are used to match strict values like IDs, national identification numbers, and so on.\n\nPartial matches\n---------------\n\nWhen you define synonyms that contain multiple words,\nDialogflow will attempt to match end-user input to the closest matching synonym,\nwhich may include partial matches.\nFor example,\nif you define a synonym as \"cold brew coffee\",\nand the end-user input is \"cold coffee\",\nthe associated entity will be matched unless there is a better match.\n\nSpell correction\n----------------\n\nWhen end-user input could be considered a misspelling of an entity synonym,\nthe associated entity may be matched.\nFor example,\nif you define a synonym as \"lumber\",\nand the end-user input is \"number\",\nthe associated entity may be matched."]]