gcloud ml language analyze-entities

NAME
gcloud ml language analyze-entities - use Google Cloud Natural Language API to identify entities in text
SYNOPSIS
gcloud ml language analyze-entities (--content=CONTENT     | --content-file=CONTENT_FILE) [--content-type=CONTENT_TYPE; default="plain-text"] [--encoding-type=ENCODING_TYPE; default="utf8"] [--language=LANGUAGE] [GCLOUD_WIDE_FLAG]
DESCRIPTION
Entity Analysis inspects the given text for common names or known entities (proper nouns such as public figures, landmarks, etc.), and returns information about those entities.

Currently English, Spanish, and Japanese are supported.

EXAMPLES
To analyze entites in raw content 'puppies':
gcloud ml language analyze-entities --content='puppies'

To analyze entites in file 'myfile.txt':

gcloud ml language analyze-entities --content-file='myfile.txt'

To analyze entites in a remote file 'gs://bucket_name/mycontent.html' for Japanese language using UTF-8 encoding:

gcloud ml language analyze-entities --content-file='gs://bucket_name/mycontent.html' --content-type=HTML --encoding-type=utf8 --language=ja-JP
REQUIRED FLAGS
Exactly one of these must be specified:
--content=CONTENT
Specify input text on the command line. Useful for experiments, or for extremely short text.
--content-file=CONTENT_FILE
Specify a local file or Google Cloud Storage (format gs://bucket/object) file path containing the text to be analyzed. More useful for longer text or data output from another system.
OPTIONAL FLAGS
--content-type=CONTENT_TYPE; default="plain-text"
Specify the format of the input text. CONTENT_TYPE must be one of: html, plain-text.
--encoding-type=ENCODING_TYPE; default="utf8"
The encoding type used by the API to calculate offsets. If set to none, encoding-dependent offsets will be set at -1. This is an optional flag only used for the entity mentions in results, and does not affect how the input is read or analyzed. ENCODING_TYPE must be one of: none, utf16, utf32, utf8.
--language=LANGUAGE
Specify the language of the input text. If omitted, the server will attempt to auto-detect. Both ISO (such as en or es) and BCP-47 (such as en-US or ja-JP) language codes are accepted.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity.

Run $ gcloud help for details.

API REFERENCE
This command uses the language/v1 API. The full documentation for this API can be found at: https://cloud.google.com/natural-language/
NOTES
These variants are also available:
gcloud alpha ml language analyze-entities
gcloud beta ml language analyze-entities