> For the complete documentation index, see [llms.txt](https://mamawhocode.gitbook.io/aws/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mamawhocode.gitbook.io/aws/services/ml/comprehend.md). # Comprehend use NLP to extract insights about the content [Document](https://docs.aws.amazon.com/comprehend/) | ## Overview * Uses natural language processing (NLP) to extract insights about the content of documents without the need of any special preprocessing. * It develops insights by recognizing * entities: people, place * key phrases * language * brand * event * sentiments (positive, negative) ### Use cases * Find documents about a subject * Find out how customers feel about your products * using `DetectSentiment` operation * it will tell you whether customers feel positive, negative, neutral, or mixed using `Sentiment` label. * Discover the topics that your customers are talking about ### Benefits * fully managed = serverless * Work greate with IAM, S3, Lambda, KMS, Kinesis Data Firehose * Discover insights * Differentiate your business * Document processing * Protect access to PII ## Features * Language support * Custom entities recognition * Custom classification * Comprehend medical --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://mamawhocode.gitbook.io/aws/services/ml/comprehend.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.