Each intent parameter has a type, called the entity type, which
dictates exactly how data from an end-user expression is extracted.
Dialogflow provides predefined system entities that can match many
common types of data. For example, there are system entities for
matching dates, times, colors, email addresses, and so on. You can
also create your own custom entities for matching custom data. For
example, you could define a vegetable entity that can match the types
of vegetables available for purchase with a grocery store agent. For
more information, see the Entity guide
<https://cloud.google.com/dialogflow/docs/entities-overview>__.
Required. The name of the entity type.
Optional. Indicates whether the entity type can be automatically expanded.
Optional. Enables fuzzy entity extraction during classification.
Classes
Entity
An entity entry for an associated entity type.
Required. A collection of value synonyms. For example, if the
entity type is vegetable, and value is scallions, a
synonym could be green onions. For KIND_LIST entity
types: - This collection must contain exactly one synonym
equal to value.