Posts

Custom Named Entity Recognition

Image
  Introduction One of the many Natural Language Processing (NLP) features provided by the Azure AI Language service is custom Named Entity Recognition (NER), also referred to as custom entity extraction. Developers can extract preset entities from text documents, like legal agreements or online advertisements, even if those documents don't follow a predetermined format thanks to Custom NER. A person, place, thing, event, ability, or value is an entity. Understand Custom Named Entity Recognition An Azure API service called Custom NER examines documents to find and extract user-defined entities. Names, locations, bank statements, and knowledge mining to enhance search results could all be examples of these things. The Azure AI Language in Azure AI services includes Custom NER. Custom vs built-in NER Azure AI Language has built-in entity identification capabilities to identify objects like people, places, organizations, or URLs. You can extract entities and build up the service with l...

Deployment Options

Image
  Deployment Options Each project can produce numerous models and deployments, each with a distinct name, thanks to Azure AI Language. Benefits include ability to: Test two models side by side Compare how the split of datasets impact performance Deploy multiple versions of your model During deployment you can choose the name for the deployed model, which can then be selected when submitting a classification task. Using REST API CLI development of Azure AI is made possible by the REST API for the Azure AI Language service. Language projects in the same manner as Language Studio offers a project-building user interface. The lab for this module delves deeper into Language Studio. Pattern of Using API For the majority of calls, the Azure AI Language service's API runs asynchronously. In each stage, we first send a request to the service and then follow up with a call to find out the status or outcome. With each request, a header is required to authenticate your request. Submit Initial ...

Understand How To Build Text Classification Projects

Image
  Introduction Your workspace for developing, honing, refining, and implementing your classification model is custom text classification projects. Language Studio and the REST API are the two methods you can work on your project. The lab will use Language Studio as the GUI, but the REST API offers the same features. The processes for creating your model are the same regardless of your preferred approach. Azure AI Language Project Life Cycle Define Labels: Understanding the data you want to classify, identify the possible labels you want to categorize into. Tag Data : Tag, or label, your existing data, specifying the label or labels each file falls under. Labeling data is important since it's how your model will learn how to classify future files. Best practice is to have clear differences between labels to avoid ambiguity, and provide good examples of each label for the model to learn from. Train Model : Train your model with the labeled data. View Model : After your model is...

Create a Custom Text Classification Solution

Image
  Introduction You may process natural language for your own application by using the Azure AI Language service. One of the most prevalent AI issues is Natural Language Processing (NLP), which requires software to perceive voice or text in the same way that people do. Text classification is a component of Natural Language Processing (NLP), and Azure offers methods for text classification that include sentiment, language, and user-defined custom categories. Understand Types of Classification Projects Text files are given labels by custom text classification, which in the Azure AI Language service is a class that the developer defines. A video game synopsis, for instance, could be categorized as "Adventure," "Strategy," "Action," or "Sports." Custom text classification falls into two types of projects: Single Label Classification - you can assign only one class to each file. Following the above example, a video game summary could only be classifie...

Intents, Utterances, and Entities (Part 2)

Image
  Use Patterns To Differentiate Similar Utterances A model may occasionally have several intents for which utterances are expected to be similar. While reducing the quantity of sample utterances, you can leverage the pattern of utterances to clarify the intents. Additionally, the intents could apply to a wide range of entity values. To correctly train your model, provide a handful of examples of each intent that specify the different formats of utterances. TurnOnDevice: "Turn on the {DeviceName}" "Switch on the {DeviceName}" "Turn the {DeviceName} on" GetDeviceStatus: "Is the {DeviceName} on[?]" TurnOffDevice: "Turn the {DeviceName} off" "Switch off the {DeviceName}" "Turn off the {DeviceName}" When you teach your model with each different type of utterance, the Azure AI Language service can learn how to categorize intents correctly based off format and punctuation. Use Pre-Built Entity Components To recognize common...

Intents, Utterances, and Entities (Part 1)

Image
  Define Intents, Utterances, and Entities When a user interacts with an application that utilizes your language model, they may enter utterances. An intent, or more simply the meaning of an utterance, is a task or activity that the user want to carry out. By defining intents and linking them to one or more utterances, you can build a model. For example, consider the following list of intents and associated utterances: GetTime: "What time is it?" "What is the time?" "Tell me the time" GetWeather: "What is the weather forecast?" "Do I need an umbrella?" "Will it snow?" TurnOnDevice "Turn the light on." "Switch on the light." "Turn on the fan" None: "Hello" "Goodbye" Spend some time thinking about the domain your model must cover and the kinds of activities or information that users might request. This will help you establish the intentions that you want your model to comprehend....

Understand Resources For Building A Conversational Language Understanding Model

Image
  About You must construct a Language resource in Azure before you can utilize the Language Understanding service to create an NLP solution. This resource will be utilized for both creating your model and handling client application prediction queries. Build Your Model   Before employing a model to generate a prediction, you must develop, train, and implement it for features that need one. The Azure AI Language service will learn what to search for from this construction and training. In the Azure portal, you must first build your Azure AI Language resource. Then: Search for Azure AI services. Find and select Language Service. Select Create under the Language Service. Fill out the necessary details, choosing the region closest to you geographically (for best performance) and giving it a unique name. Once that resource has been created, you will need a key and the endpoint. You can find that on the left side under Keys and Endpoint of the resource overview page. Use Language St...