The Qwen Large Model is an intelligent data processing tool within the AI-Large Model Processing Operator. By configuring custom model settings, generation strategies, and persona, it enables unstructured data parsing, multilingual translation, and other functions, making it suitable for enterprise intelligent data processing scenarios. This document introduces how to use the Qwen Large Model operator.
Click 'Custom Model', and in the 'Model Settings' pop-up window, configure the relevant parameters.
The relevant parameter descriptions are as follows:
Parameters | Configuration instructions |
|---|---|
Model | If the enterprise administrator has already configured a large model for the operator (see Prerequisites for details), you can select the large model. You can also select a Custom Model and complete the relevant model configuration. |
Model Invocation Address | If you select a Custom Model, you must fill in the application's invocation address. |
Inference Endpoint | If you select a Custom Model, you must configure the inference endpoint. The typical format is |
API Key | If you select a Custom Model, you must configure the API Key. The typical format is |
Generation Diversity | Four modes are supported to adjust generation randomness and Top P values, enabling control over the effects of the large model operator.
tip
|
Users can customize the persona, functions, and workflows of the large model.
Use natural language to specify the persona, functions, and workflows of the large model. You may refer to the following content for custom configuration:
# Role You are a precise and efficient intelligent delivery address resolution assistant robot that can accurately and efficiently parse input address information into structured content. For any input address, the parsing result must be quickly and accurately returned in JSON format.{ /** Province */ "province": "string", /** City */ "city": "string", /** District */ "region": "string", /** Detailed Address */ "address": "string", /** Recipient */ "people": "string", /** Phone */ "tel": "string" } ## Skill ### Skill 1: address resolution 1. Carefully analyze the input address text and extract key information such as province, city, district, detailed address, recipient, and phone number. 2. For vague or incomplete address information, try to supplement and improve it through reasonable speculation and common address patterns. ## Restrictions: - Only handle tasks related to express address resolution and refuse to handle other unrelated content. - Strictly output the results in the given JSON format without any deviation. - For unresolved or ambiguous address information, null can be output.
Users can select upstream fields or system variables as template variables and embed them into user input. For example, by using the upstream content field and entering '${content}' in the user input, the large model will process the content of the content field.
This includes upstream fields and system variables.
Upstream fields: Use ${field name} to reference data from upstream fields, and use
Type | Identifier |
|---|---|
Text |
|
Image |
|
Audio |
|
Video |
|
No identifier specified | The system default is |
System variables: Use ${system variable name} to reference system variables, for example ${date}. Variables support date addition and subtraction, such as ${date - 1}, which represents the previous day.
warning
Configure user input as sample content for data post-processing and field configuration test execution.
Click "Advanced Settings" to configure relevant parameters.
The relevant parameter descriptions are as follows:
Parameters | configuration instructions |
|---|---|
Parallelism | The number of parallel requests; actual parallelism also depends on available cluster resources. Users are advised to calculate and fill in parallelism based on the performance limits of the called interface (such as QPS, QPM, etc.). |
Timeout | Timeout for large model computation, measured in milliseconds (ms). |
Retry Count | Automatic retry count for failed requests, number of times. |
Request Interval | Large model endpoints typically have an RPM (requests per minute) limit. Set the request interval as needed based on the RPM value, measured in milliseconds (ms). tip Setting a request interval is intended to prevent rate limit errors from large models; typical error messages are as follows. |
Completion Exception Handling |
|
Click "Test Execution" and view the output results in the "Test Execution Results" section.
Select "Data Post-Processing" to process data based on the output results of the large model (API). Click "Test Execution" to test the results of data post-processing, which can be viewed in the "Test Execution Results" section.
Configure fields, parsing paths, and field types based on the test execution results to structure the output data.