หน้านี้ยังไม่พร้อมใช้งานในภาษาท้องถิ่นของคุณ เรากำลังพยายามอย่างหนักเพื่อเพิ่มเวอร์ชันภาษาอื่น ๆ เพิ่มเติม ขอบคุณสำหรับการสนับสนุนเสมอมา

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
Software Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Adding Entities

Updated on 2024-10-12 GMT+08:00

Entities are variables or parameters, which can be used to configure multiple dialogs of a task-oriented robot to recognize specific customer purposes. They can also be used to temporarily store parameter values in interfaces for future calculation. For example, when a customer needs to purchase a flight ticket, you need to know the departure city, destination city, departure time, and flight company for the flight. The departure city, arrival city, departure time, and flight company can be considered as entities.

Context

Entities can impose specification constraints on the values filled in a slot, similar to defining data types for variables. Some entities are preset, such as system.date, system.time, system.number, and system.phonekeyboard. You can view entities on SYSTEM ENTITY and ENVIRONMENT ENTITY (by choosing Template Management > Entity Management). You can also click Test Entity under My Entity to check whether the variables that you need can be recognized. If the preset entities do not meet your requirements, customize your entities. Customer entities are classified into the following types:

  • General entity: entity corresponding to a single variable. For example, a departure city, a destination city, and a flight company are general entities. For customized general entities, only enumerated values and their synonyms can be set. Complex functions such as fuzzy match cannot be implemented.
  • Composite entity: combination of multiple entities. For example, an identity entity, a city entity, a region entity, and a street entity form a mailing address entity together. Composite entities are usually used to define complex and structured texts.
  • Rule entity: entity that defines a fixed format (prefix and suffix), and part-of-speech rules. When a type of entity has fixed features in sentence expressions, for example, all entities have the same prefix or suffix, you can define a rule entity to expand the capture range of this entity.

During the application of an entity, the system matches the entity values with customer statements. If the matching is successful, the system considers that the entities are contained in the customer statements and uses the entity values for subsequent processing.

Configuring a General Entity

To add a flight company entity, perform the following steps:

  1. Choose Configuration Center > Chatbot Management > Semantic Understanding.
  2. Choose Knowledge Management > Entity Management. Click Create, and choose General entity.
  3. Set Name, click Create to add entity values and their synonyms, and click Save.

  4. Click Test Entity in the upper right corner, and enter an entity value or synonym in the text box. If the AI robot returns @Flight Company=Emirates, the configuration takes effect.

Configuring a Composite Entity

You need to add a location entity that indicates the direction and distance, for example, 100 meters eastwards.

  1. Choose Configuration Center > Chatbot Management > Semantic Understanding.
  2. Choose Knowledge Management > Entity Management. Add a general entity that indicates a direction by referring to Configuring a General Entity. A direction entity includes four elements: East, West, South, and North.
  3. Click Create, and choose Composite entity.
  4. Set Name, and click .
  5. Configure a composite entity.

    1. Select the entity added in 2 from the drop-down list.
    2. Click to add the second drop-down list, and select @system.number (indicating a number) from the drop-down list.
    3. Click to add the third drop-down list, hover the pointer over the drop-down list, click next to the drop-down list to switch from the entity selection mode to the text input mode, and enter Meter.

  6. Click Save.

Configuring a Rule Entity

You need to add a rule entity to identify a company name entity of XXX Co., Ltd.

  1. Choose Configuration Center > Chatbot Management > Semantic Understanding.
  2. Choose Knowledge Management > Entity Management. Click Create, and choose Rule entity.
  3. Set Name.
  4. Set parameters as follows:

    A rule supports the following filtering of a character string:

    • If both Part-of-speech and Suffix are set, the character string that meets the part-of-speech requirement is obtained after the suffix is matched. The length of the character string cannot exceed the value of Maximum length.

      In addition to common adjectives, nouns, numbers, and quantifiers, special nouns are further classified into the following types.

      • Gerund: If you use phrases that can be used as verbs to compose the name of an entity, for example, XX Daily Wholesale Co., Ltd., you can set Part-of-speech to Gerund to better match the entity.
      • Localizer: Without the prefix and suffix, the remaining characters indicate a localizer such as front, back, upper, and lower.
      • OU name: Without the prefix and suffix, the remaining characters indicate an OU group.
      • Place name: Without the prefix and suffix, the remaining characters indicate a city and province.
    • If Part-of-speech is not set, characters between the prefix and suffix are used. The length cannot exceed the value of Maximum length.

      Exact Matching determines whether the prefix and suffix are used for matching.

      Include Prefix In Entity Result and Include Suffix In Entity Result determine whether information corresponding to the prefix and suffix is used as the entity content. For example, in this example, Include Suffix in Entity Result needs to be enabled. The matched entity is XX Co., Ltd.

  5. Click Save.

เราใช้คุกกี้เพื่อปรับปรุงไซต์และประสบการณ์การใช้ของคุณ การเรียกดูเว็บไซต์ของเราต่อแสดงว่าคุณยอมรับนโยบายคุกกี้ของเรา เรียนรู้เพิ่มเติม

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback