POST
/
ai
/
async-chunking
/
semantic
/
{MODEL_ID}
semantic by modelId
curl --request POST \
  --url https://application_id.applications.lucidworks.com/ai/async-chunking/semantic/{MODEL_ID} \
  --header 'Content-Type: application/json' \
  --data '{
  "batch": [
    {
      "text": "The content to be split into chunks. "
    }
  ],
  "modelConfig": {
    "vectorQuantizationMethod": "min-max or max-scale",
    "dimReductionSize": 256
  },
  "useCaseConfig": {
    "dataType": "query"
  },
  "chunkerConfig": {
    "maxChunkSize": 512,
    "overlapSize": 1,
    "cosineThreshold": 0.567,
    "approximate": true
  }
}'
{
  "chunkingId": "441eb3be-7de6-470a-8141-e416a15c7db1",
  "status": "SUBMITTED"
}

Headers

​
Authorization: Bearer ACCESS_TOKEN
string

The authentication and authorization access token.

​
Content-Type
string

application/json

Example:

"application/json"

Path Parameters

​
MODEL_ID
string
required

Unique identifier for the model.

Example:

"gte-small"

Body

application/json
​
batch
object[]

The batch of key:value pairs used in the chunking request.

​
modelConfig
object

Provides fields and values that specify ranges for tokens.

​
useCaseConfig
object
​
chunkerConfig
object

The semantic chunker (chunking strategy) creates chunks based on semantic similarity.

Using the model defined in the URL request, the semantic chunker splits text into sentences, encodes the sentences, and then compares the sentence to the building chunk to determine if they are similar enough to group together.

After merging two semantically-similar sentences into a pre-chunk, the semantic chunker needs to encode it to get its vector to compare with the next sentence vector.

This chunker is the slowest of all of the chunkers even if you set the approximate field to true.

This is the default chunker configuration if nothing is passed.

Response

OK

This is the response to the POST chunking request submitted for a specific chunker and modelId.

​
chunkingId
string<uuid>

The universal unique identifier (UUID) returned in the POST request. This UUID is required in the GET request to retrieve results.

Example:

"441eb3be-7de6-470a-8141-e416a15c7db1"

​
status
string

The current status of the request. Allowed values are:

  • SUBMITTED - The POST request was successful and the response has returned the chunkingId and status that is used by the GET request.

  • ERROR - An error was generated when the GET request was sent.

  • READY - The results associated with the chunkingId are available and ready to be retrieved.

  • RETRIEVED - The results associated with the chunkingId are returned successfully when the GET request was sent.

Example:

"SUBMITTED"