gcloud beta ml language analyze-entities - use Google Cloud Natural Language API to identify entities in text

gcloud beta 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 …]

Currently English, Spanish, Japanese, Chinese (Simplified and Traditional),French, German, Italian, Korean, and Portuguese are supported.

gcloudbetamllanguageanalyze-entities--content='puppies'

To analyze entites in file 'myfile.txt':

gcloudbetamllanguageanalyze-entities--content-file='myfile.txt'

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

gcloudbetamllanguageanalyze-entities--content-file='gs://bucket_name/mycontent.html'--content-type=HTML--encoding-type=utf8--language=ja-JP

Exactly one of these must be specified:

--content=CONTENT

Specify input text on the command line. Useful for experiments, or for extremelyshort text.

--content-file=CONTENT_FILE

Specify a local file or Google Cloud Storage (formatgs://bucket/object) file path containing the text to be analyzed.More useful for longer text or data output from another system.

--content-type=CONTENT_TYPE; default="plain-text"

Specify the format of the input text.CONTENT_TYPE mustbe one of:html,plain-text.

--encoding-type=ENCODING_TYPE; default="utf8"

The encoding type used by the API to calculate offsets. If set tonone, encoding-dependent offsets will be set at -1. This is anoptional flag only used for the entity mentions in results, and does not affecthow the input is read or analyzed.ENCODING_TYPE must beone of:none,utf16,utf32,utf8.

--language=LANGUAGE

Specify the language of the input text. If omitted, the server will attempt toauto-detect. Both ISO (such asen ores) and BCP-47(such asen-US orja-JP) language codes are accepted.

Run$gcloud help for details.