Module aws_sdk_comprehend::types
source · Expand description
Data structures used by operation inputs/outputs.
Modules
- Builders
- Error types that Amazon Comprehend can respond with.
Structs
An augmented manifest file that provides training data for your custom model. An augmented manifest file is a labeled dataset that is produced by Amazon SageMaker Ground Truth.
The result of calling the operation. The operation returns one object for each document that is successfully processed by the operation.
The result of calling the operation. The operation returns one object for each document that is successfully processed by the operation.
The result of calling the operation. The operation returns one object for each document that is successfully processed by the operation.
The result of calling the operation. The operation returns one object for each document that is successfully processed by the operation.
The result of calling the operation. The operation returns one object that is successfully processed by the operation.
Analysis results for one of the documents in the batch.
Describes an error that occurred while processing a document in a batch. The operation returns on
BatchItemError
object for each document that contained an error.Information about each word or line of text in the input document.
A reference to a block.
The bounding box around the detected page or around an element on a document page. The left (x-coordinate) and top (y-coordinate) are coordinates that represent the top and left sides of the bounding box. Note that the upper-left corner of the image is the origin (0,0).
Nested block contained within a block.
Describes the result metrics for the test data associated with an documentation classifier.
Provides information about a document classifier.
Data security configuration.
An augmented manifest file that provides training data for your custom model. An augmented manifest file is a labeled dataset that is produced by Amazon SageMaker Ground Truth.
Describes the dataset input data configuration for a document classifier model.
Describes the annotations associated with a entity recognizer.
Describes the documents submitted with a dataset for an entity recognizer model.
Describes the dataset entity list for an entity recognizer model.
Specifies the format and location of the input data. You must provide either the
Annotations
parameter or theEntityList
parameter.Filter the datasets based on creation time or dataset status.
Specifies the format and location of the input data for the dataset.
Properties associated with the dataset.
Specifies the class that categorizes the document being analyzed
Configuration required for a document classification model.
Provides information for filtering a list of document classification jobs. For more information, see the operation. You can provide only one filter parameter in each request.
Provides information about a document classification job.
The location of the training documents. This parameter is required in a request to create a semi-structured document classification model.
Provides information for filtering a list of document classifiers. You can only specify one filtering parameter in a request. For more information, see the
ListDocumentClassifiers
operation.The input properties for training a document classifier.
Provide the location for output data from a custom classifier job. This field is mandatory if you are training a native document model.
Provides information about a document classifier.
Describes information about a document classifier and its versions.
Specifies one of the label or labels that categorize the document being analyzed.
Information about the document, discovered during text extraction.
Provides configuration parameters to override the default actions for extracting text from PDF documents and image files.
Document type for each page in the document.
Returns the code for the dominant language in the input text and the level of confidence that Amazon Comprehend has in the accuracy of the detection.
Provides information for filtering a list of dominant language detection jobs. For more information, see the operation.
Provides information about a dominant language detection job.
The filter used to determine which endpoints are returned. You can filter jobs on their name, model, status, or the date and time that they were created. You can only set one filter at a time.
Specifies information about the specified endpoint. For information about endpoints, see Managing endpoints.
Provides information for filtering a list of dominant language detection jobs. For more information, see the operation.
Provides information about an entities detection job.
Provides information about an entity.
Specifies one of the label or labels that categorize the personally identifiable information (PII) entity being analyzed.
Configuration required for an entity recognition model.
Describes the annotations associated with a entity recognizer.
Describes the training documents submitted with an entity recognizer.
Describes the entity list submitted with an entity recognizer.
Detailed information about the accuracy of an entity recognizer.
Provides information for filtering a list of entity recognizers. You can only specify one filtering parameter in a request. For more information, see the
ListEntityRecognizers
operation./>Specifies the format and location of the input data.
Detailed information about an entity recognizer.
Individual item from the list of entity types in the metadata of an entity recognizer.
Output data configuration.
Describes information about an entity recognizer.
Describes the information about an entity recognizer and its versions.
Detailed information about the accuracy of an entity recognizer for a specific entity type.
An entity type within a labeled training dataset that Amazon Comprehend uses to train a custom entity recognizer.
Text extraction encountered one or more page-level errors in the input document.
Provides information for filtering a list of event detection jobs.
Provides information about an events detection job.
Array of the number of characters extracted from each page.
Filter the flywheels based on creation time or flywheel status.
Filter the flywheel iterations based on creation time.
The configuration properties of a flywheel iteration.
The evaluation metrics associated with the evaluated model.
The flywheel properties.
Flywheel summary information.
Information about the location of items on a document page.
The input properties for an inference job. The document reader config field applies only to non-text inputs for custom analysis.
Provides additional detail about why the request failed:
Describes a key noun phrase.
Provides information for filtering a list of dominant language detection jobs. For more information, see the operation.
Provides information about a key phrases detection job.
Contains the sentiment and sentiment score for one mention of an entity.
Provides configuration parameters for the output of inference jobs.
Identifies the part of speech represented by the token and gives the confidence that Amazon Comprehend has that the part of speech was correctly identified. For more information about the parts of speech that Amazon Comprehend can identify, see Syntax in the Comprehend Developer Guide.
Provides information for filtering a list of PII entity detection jobs.
Provides information about a PII entities detection job.
Provides information about a PII entity.
Provides configuration parameters for the output of PII entity detection jobs.
The X and Y coordinates of a point on a document page.
Provides configuration parameters for PII entity redaction.
List of child blocks for the current block.
Provides information for filtering a list of dominant language detection jobs. For more information, see the operation.
Provides information about a sentiment detection job.
Describes the level of confidence that Amazon Comprehend has in the accuracy of its detection of sentiments.
Represents a work in the input text that was recognized and assigned a part of speech. There is one syntax token record for each word in the source text.
A key-value pair that adds as a metadata to a resource used by Amazon Comprehend. For example, a tag with the key-value pair ‘Department’:’Sales’ might be added to a resource to indicate its use by a particular department.
Provides information for filtering a list of dominant language detection jobs. For more information, see the
ListTargetedSentimentDetectionJobs
operation.Provides information about a targeted sentiment detection job.
Information about one of the entities found by targeted sentiment analysis.
Information about one mention of an entity. The mention information includes the location of the mention in the text and the sentiment of the mention.
Configuration about the model associated with a flywheel.
One of the of text strings. Each string has a size limit of 1KB.
Provides information for filtering topic detection jobs. For more information, see .
Provides information about a topic detection job.
Toxic content analysis result for one string. For more information about toxicity detection, see Toxicity detection in the Amazon Comprehend Developer Guide
Toxicity analysis result for one string. For more information about toxicity detection, see Toxicity detection in the Amazon Comprehend Developer Guide
Data security configuration.
Configuration parameters for an optional private Virtual Private Cloud (VPC) containing the resources you are using for the job. For more information, see Amazon VPC.
The system identified one of the following warnings while processing the input document:
Enums
- When writing a match expression against
AugmentedManifestsDocumentTypeFormat
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
BlockType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DatasetDataFormat
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DatasetStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DatasetType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DocumentClassifierDataFormat
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DocumentClassifierDocumentTypeFormat
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DocumentClassifierMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DocumentReadAction
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DocumentReadFeatureTypes
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DocumentReadMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DocumentType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
EndpointStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
EntityRecognizerDataFormat
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
EntityType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
FlywheelIterationStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
FlywheelStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
InputFormat
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
InvalidRequestDetailReason
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
InvalidRequestReason
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
JobStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
LanguageCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ModelStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ModelType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PageBasedErrorCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PageBasedWarningCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PartOfSpeechTagType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PiiEntitiesDetectionMaskMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PiiEntitiesDetectionMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PiiEntityType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
RelationshipType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
SentimentType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Split
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
SyntaxLanguageCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TargetedSentimentEntityType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ToxicContentType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.