Important
Input documents for event extraction should be no larger than 4K characters.
Do you know the language of your input?
If you know the language of your input, include the three-letter language code in your call. This will speed up the response time.
Otherwise, Rosette will identify the language automatically.
While Rosette will identify the language automatically, if the language is misidentified, the correct events model will not be used. We recommend you include the language code in your call, where possible.
If no language is provided, and Rosette is unable to auto-detect it, an endpoint may provide a “Language xxx is not supported” error, where xxx indicates the language was not determined.
Either workspaceId or plan can be provided as an option. Both cannot be used in the same call. When using plan, the workspaceId is provided within the plan.
Example 1. Single event model request
Only a single event extraction model is called.
{
"content": "string",
"language": "string",
"options": {
"workspaceId": "string"
}
Example 2. All event models request
All event extraction models that match the language of the content string are called. Multiple event mentions may be returned, from different event models.
{
"content": "string",
"language": "string",
}
Example 3. Multiple event model request
Multiple event extraction models are called in a single request. Only the models where the languageCode matches the language of the content string are called. Multiple event mentions may be returned, from different event models.
{
"content": "string",
"language": "string",
"options": {
"plan": {
"languageCode": [
"workspaceId": "string"
]
}
}