Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Augmented
Manifests List Item 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.
- Batch
Detect Dominant Language Item Result The result of calling the operation. The operation returns one object for each document that is successfully processed by the operation.
- Batch
Detect Entities Item Result The result of calling the operation. The operation returns one object for each document that is successfully processed by the operation.
- Batch
Detect KeyPhrases Item Result The result of calling the operation. The operation returns one object for each document that is successfully processed by the operation.
- Batch
Detect Sentiment Item Result The result of calling the operation. The operation returns one object for each document that is successfully processed by the operation.
- Batch
Detect Syntax Item Result The result of calling the operation. The operation returns one object that is successfully processed by the operation.
- Batch
Detect Targeted Sentiment Item Result Analysis results for one of the documents in the batch.
- Batch
Item Error 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.- Block
Information about each word or line of text in the input document.
For additional information, see Block in the Amazon Textract API reference.
- Block
Reference A reference to a block.
- Bounding
Box 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).
For additional information, see BoundingBox in the Amazon Textract API reference.
- Child
Block Nested block contained within a block.
- Classifier
Evaluation Metrics Describes the result metrics for the test data associated with an documentation classifier.
- Classifier
Metadata Provides information about a document classifier.
- Data
Security Config Data security configuration.
- Dataset
Augmented Manifests List Item 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.
- Dataset
Document Classifier Input Data Config Describes the dataset input data configuration for a document classifier model.
For more information on how the input file is formatted, see Preparing training data in the Comprehend Developer Guide.
- Dataset
Entity Recognizer Annotations Describes the annotations associated with a entity recognizer.
- Dataset
Entity Recognizer Documents Describes the documents submitted with a dataset for an entity recognizer model.
- Dataset
Entity Recognizer Entity List Describes the dataset entity list for an entity recognizer model.
For more information on how the input file is formatted, see Preparing training data in the Comprehend Developer Guide.
- Dataset
Entity Recognizer Input Data Config Specifies the format and location of the input data. You must provide either the
Annotations
parameter or theEntityList
parameter.- Dataset
Filter Filter the datasets based on creation time or dataset status.
- Dataset
Input Data Config Specifies the format and location of the input data for the dataset.
- Dataset
Properties Properties associated with the dataset.
- Document
Class Specifies the class that categorizes the document being analyzed
- Document
Classification Config Configuration required for a document classification model.
- Document
Classification JobFilter 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.
- Document
Classification JobProperties Provides information about a document classification job.
- Document
Classifier Documents The location of the training documents. This parameter is required in a request to create a semi-structured document classification model.
- Document
Classifier Filter 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.- Document
Classifier Input Data Config The input properties for training a document classifier.
For more information on how the input file is formatted, see Preparing training data in the Comprehend Developer Guide.
- Document
Classifier Output Data Config Provide the location for output data from a custom classifier job. This field is mandatory if you are training a native document model.
- Document
Classifier Properties Provides information about a document classifier.
- Document
Classifier Summary Describes information about a document classifier and its versions.
- Document
Label Specifies one of the label or labels that categorize the document being analyzed.
- Document
Metadata Information about the document, discovered during text extraction.
- Document
Reader Config Provides configuration parameters to override the default actions for extracting text from PDF documents and image files.
By default, Amazon Comprehend performs the following actions to extract text from files, based on the input file type:
-
Word files - Amazon Comprehend parser extracts the text.
-
Digital PDF files - Amazon Comprehend parser extracts the text.
-
Image files and scanned PDF files - Amazon Comprehend uses the Amazon Textract
DetectDocumentText
API to extract the text.
DocumentReaderConfig
does not apply to plain text files or Word files.For image files and PDF documents, you can override these default actions using the fields listed below. For more information, see Setting text extraction options in the Comprehend Developer Guide.
-
- Document
Type List Item Document type for each page in the document.
- Dominant
Language 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.
- Dominant
Language Detection JobFilter Provides information for filtering a list of dominant language detection jobs. For more information, see the operation.
- Dominant
Language Detection JobProperties Provides information about a dominant language detection job.
- Endpoint
Filter 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.
- Endpoint
Properties Specifies information about the specified endpoint. For information about endpoints, see Managing endpoints.
- Entities
Detection JobFilter Provides information for filtering a list of dominant language detection jobs. For more information, see the operation.
- Entities
Detection JobProperties Provides information about an entities detection job.
- Entity
Provides information about an entity.
- Entity
Label Specifies one of the label or labels that categorize the personally identifiable information (PII) entity being analyzed.
- Entity
Recognition Config Configuration required for an entity recognition model.
- Entity
Recognizer Annotations Describes the annotations associated with a entity recognizer.
- Entity
Recognizer Documents Describes the training documents submitted with an entity recognizer.
- Entity
Recognizer Entity List Describes the entity list submitted with an entity recognizer.
- Entity
Recognizer Evaluation Metrics Detailed information about the accuracy of an entity recognizer.
- Entity
Recognizer Filter 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./>- Entity
Recognizer Input Data Config Specifies the format and location of the input data.
- Entity
Recognizer Metadata Detailed information about an entity recognizer.
- Entity
Recognizer Metadata Entity Types List Item Individual item from the list of entity types in the metadata of an entity recognizer.
- Entity
Recognizer Output Data Config Output data configuration.
- Entity
Recognizer Properties Describes information about an entity recognizer.
- Entity
Recognizer Summary Describes the information about an entity recognizer and its versions.
- Entity
Types Evaluation Metrics Detailed information about the accuracy of an entity recognizer for a specific entity type.
- Entity
Types List Item An entity type within a labeled training dataset that Amazon Comprehend uses to train a custom entity recognizer.
- Errors
List Item Text extraction encountered one or more page-level errors in the input document.
The
ErrorCode
contains one of the following values:-
TEXTRACT_BAD_PAGE - Amazon Textract cannot read the page. For more information about page limits in Amazon Textract, see Page Quotas in Amazon Textract.
-
TEXTRACT_PROVISIONED_THROUGHPUT_EXCEEDED - The number of requests exceeded your throughput limit. For more information about throughput quotas in Amazon Textract, see Default quotas in Amazon Textract.
-
PAGE_CHARACTERS_EXCEEDED - Too many text characters on the page (10,000 characters maximum).
-
PAGE_SIZE_EXCEEDED - The maximum page size is 10 MB.
-
INTERNAL_SERVER_ERROR - The request encountered a service issue. Try the API request again.
-
- Events
Detection JobFilter Provides information for filtering a list of event detection jobs.
- Events
Detection JobProperties Provides information about an events detection job.
- Extracted
Characters List Item Array of the number of characters extracted from each page.
- Flywheel
Filter Filter the flywheels based on creation time or flywheel status.
- Flywheel
Iteration Filter Filter the flywheel iterations based on creation time.
- Flywheel
Iteration Properties The configuration properties of a flywheel iteration.
- Flywheel
Model Evaluation Metrics The evaluation metrics associated with the evaluated model.
- Flywheel
Properties The flywheel properties.
- Flywheel
Summary Flywheel summary information.
- Geometry
Information about the location of items on a document page.
For additional information, see Geometry in the Amazon Textract API reference.
- Input
Data Config The input properties for an inference job. The document reader config field applies only to non-text inputs for custom analysis.
- Invalid
Request Detail Provides additional detail about why the request failed.
- KeyPhrase
Describes a key noun phrase.
- KeyPhrases
Detection JobFilter Provides information for filtering a list of dominant language detection jobs. For more information, see the operation.
- KeyPhrases
Detection JobProperties Provides information about a key phrases detection job.
- Mention
Sentiment Contains the sentiment and sentiment score for one mention of an entity.
For more information about targeted sentiment, see Targeted sentiment in the Amazon Comprehend Developer Guide.
- Output
Data Config Provides configuration parameters for the output of inference jobs.
- Part
OfSpeech Tag 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.
- PiiEntities
Detection JobFilter Provides information for filtering a list of PII entity detection jobs.
- PiiEntities
Detection JobProperties Provides information about a PII entities detection job.
- PiiEntity
Provides information about a PII entity.
- PiiOutput
Data Config Provides configuration parameters for the output of PII entity detection jobs.
- Point
The X and Y coordinates of a point on a document page.
For additional information, see Point in the Amazon Textract API reference.
- Redaction
Config Provides configuration parameters for PII entity redaction.
- Relationships
List Item List of child blocks for the current block.
- Sentiment
Detection JobFilter Provides information for filtering a list of dominant language detection jobs. For more information, see the operation.
- Sentiment
Detection JobProperties Provides information about a sentiment detection job.
- Sentiment
Score Describes the level of confidence that Amazon Comprehend has in the accuracy of its detection of sentiments.
- Syntax
Token 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.
- Tag
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.
- Targeted
Sentiment Detection JobFilter Provides information for filtering a list of dominant language detection jobs. For more information, see the
ListTargetedSentimentDetectionJobs
operation.- Targeted
Sentiment Detection JobProperties Provides information about a targeted sentiment detection job.
- Targeted
Sentiment Entity Information about one of the entities found by targeted sentiment analysis.
For more information about targeted sentiment, see Targeted sentiment in the Amazon Comprehend Developer Guide.
- Targeted
Sentiment Mention 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.
For more information about targeted sentiment, see Targeted sentiment in the Amazon Comprehend Developer Guide.
- Task
Config Configuration about the model associated with a flywheel.
- Text
Segment One of the of text strings. Each string has a size limit of 1KB.
- Topics
Detection JobFilter Provides information for filtering topic detection jobs. For more information, see .
- Topics
Detection JobProperties Provides information about a topic detection job.
- Toxic
Content Toxic content analysis result for one string. For more information about toxicity detection, see Toxicity detection in the Amazon Comprehend Developer Guide
- Toxic
Labels Toxicity analysis result for one string. For more information about toxicity detection, see Toxicity detection in the Amazon Comprehend Developer Guide.
- Update
Data Security Config Data security configuration.
- VpcConfig
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.
- Warnings
List Item The system identified one of the following warnings while processing the input document:
-
The document to classify is plain text, but the classifier is a native document model.
-
The document to classify is semi-structured, but the classifier is a plain-text model.
-
Enums§
- Augmented
Manifests Document Type Format - 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. - Block
Type - 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. - Dataset
Data Format - 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. - Dataset
Status - 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. - Dataset
Type - 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. - Document
Classifier Data Format - 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. - Document
Classifier Document Type Format - 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. - Document
Classifier Mode - 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. - Document
Read Action - 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. - Document
Read Feature Types - 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. - Document
Read Mode - 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. - Document
Type - 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. - Endpoint
Status - 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. - Entity
Recognizer Data Format - 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. - Entity
Type - 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. - Flywheel
Iteration Status - 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. - Flywheel
Status - 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. - Input
Format - 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. - Invalid
Request Detail Reason - 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. - Invalid
Request Reason - 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. - JobStatus
- 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. - Language
Code - 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. - Model
Status - 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. - Model
Type - 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. - Page
Based Error Code - 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. - Page
Based Warning Code - 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. - Part
OfSpeech TagType - 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. - PiiEntities
Detection Mask Mode - 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. - PiiEntities
Detection Mode - 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. - PiiEntity
Type - 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. - Relationship
Type - 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. - Sentiment
Type - 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. - Split
- 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. - Syntax
Language Code - 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. - Targeted
Sentiment Entity Type - 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. - Toxic
Content Type - 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.