You need to enable JavaScript to run this app.
DataAgent (OnPremise)

DataAgent (OnPremise)

Copy page
Download PDF
AI-Large Model Processing
Qwen Large Model
Copy page
Download PDF
Qwen Large Model

Function Overview

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.

Prerequisites
  • You have activated the Tongyi Qwen Large Model service or other custom large model services.
  • The enterprise administrator has configured a large model for the operator. For details, please refer to Configure Large Model Invocation.

Instructions

Step 1: Create a Qwen Large Model Operator

  1. Click 'Data Integration', select 'Visual Knowledge Processing', click 'New', and then select 'Create Offline Task'.
    Image
  2. Follow the steps in Offline Task Creation to complete Task Creation. At the processing node, select the Qwen Large Model operator from 'AI-Large Model Processing' to add to the Data Connection.
    Image

Step 2: Set Model Integration Parameters

Click 'Custom Model', and in the 'Model Settings' pop-up window, configure the relevant parameters.
Image
Image
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 ep-xxxxxxxxxx-yyyy. For creation instructions, refer to Create Custom Inference Endpoint.

API Key

If you select a Custom Model, you must configure the API Key. The typical format is xxxxxxxx-yyyy-xxxx-yyyy-xxxxxxxxxxxx. For instructions on obtaining it, refer to Obtain and Configure API Key.

Generation Diversity

Four modes are supported to adjust generation randomness and Top P values, enabling control over the effects of the large model operator.

  • Precise Mode:
    • Strictly follows instructions to generate content.
    • Suitable for scenarios requiring absolute accuracy, such as official documents and code.
  • Balanced Mode:
    • Seeks a balance between innovation and precision.
    • Applicable to most daily application scenarios, generating content that is interesting yet rigorous.
  • Creative Mode:
    • Stimulate creativity and provide novel, unique ideas.
    • Suitable for scenarios requiring inspiration and distinctive perspectives, such as brainstorming and creative writing.
  • Custom Mode:
    • Customize the generation method through advanced settings.
    • Fine-tune according to requirements to achieve personalized optimization.

tip

  • Generation Randomness: Increasing this parameter enhances the diversity and creativity of model outputs; conversely, decreasing it makes outputs more compliant with instructions but reduces diversity. It is recommended not to adjust 'Top p' simultaneously.
  • Top p: Cumulative probability. When generating output, the model selects words with the highest probability until their cumulative probability reaches the Top p value. This restricts the model to selecting only these high-probability words, thereby controlling output diversity. It is recommended not to adjust 'Generation Randomness' simultaneously.

Step 3: Configure Model Persona and Response Logic

Users can customize the persona, functions, and workflows of the large model.
Image
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.  

Step 4: Configure Template Variables

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.
Image
This includes upstream fields and system variables.

  • Upstream fields: Use ${field name} to reference data from upstream fields, and use to indicate the input content type. For example, ${context} is used to reference data from the upstream content column, which is of text type. The following identifiers are currently supported:

    Type

    Identifier

    Text

    <text>

    Image

    <image>

    Audio

    <audio>

    Video

    <video>

    No identifier specified

    The system default is <text>

  • 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

    • If the upstream field name is identical to a system variable, it will be overwritten by the system variable.
    • Ensure that Image, Audio, Video, and URLs are accessible.

Step Five: Configure User Input

Configure user input as sample content for data post-processing and field configuration test execution.
Image

Step Six: Advanced Settings

Click "Advanced Settings" to configure relevant parameters.
Image
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.
Image

Completion Exception Handling

  • Terminate Task: If inference fails, the task will fail and intermediate results will be cleared.
  • Ignore Exception: In tolerant mode, failed inference data is ignored, filled with null, and successful inference results are retained.

Step Seven: Test Execution

Click "Test Execution" and view the output results in the "Test Execution Results" section.
Image

Step Eight: Data Post-Processing Configuration

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.
Image

Step Nine: Field Configuration

Configure fields, parsing paths, and field types based on the test execution results to structure the output data.
Image

Last updated: 2026.06.30 14:26:21