KnowledgeAnswersIntentQueryArgumentSignals

The gaia id for the entity (person or plus page).

Status indicating whether the user has completely expressed the semantics of the argument.

A list of mids that "support" this argument in voting, i.e., results that support these mids will be treated as if they support the argument. This field has been deprecated in favor of related_entity. b/27363861

Additional signals for on-device annotations.

Type of ungrounded argument. It is exclusively used when simple_value.ungrounded_value is populated.

Whether this argument was annotated by Intentgen QUIK model (go/intentgen-quik)

Confidence score of this argument being a location.

For this argument, backend performed fuzzy match.

Set when the eval_data was not derived at parsing time, but heuristically determined by matching the ArgumentValue to an annotation/query fragment.

Support Transfer signals for this entity.

If the literal.obj_type of the argument value is ID (Entity), this represents freebase types of the entity in this argument.

A copy of the span of canonical (raw) parser input text corresponding to this annotation.

Set when the argument has an enum value - a normalized_string_type from the intent catalog.

go/stbr supportthis is an

The index of the QueryJoin interpretation from which this annotation is taken. We copy over the value given by nlp.semantic_parsing.annotators.QrefAnnotator. The value will be "-1" if the annotation is coming from low confidence Qref annotations. NOTE - this is generated from as QRef's interetation_number.

Relatedness Matrix signals about this argument, e.g., query_popularity.

The type category for the location stored in this Argument, if it exists.

List of QRef implied entities merged into this entity during parsing. Clients should not rely on the order, as it is derivation-dependent.

Whether there were multiple equally good matches from horizontal_list_selection.

For collection arguments, it is useful to save what was the original mid that qref annotated. For example, if the collection is /collection/films, we'll have the mid for /en/film here (/m/02vxn).

Signals derived from SAFT.

List of entities that are semantically related to the argument as well as details of the relationship.

Personal entities are compound entities made up of entities and their attributes, where the entities can be compound too. E.g., "my father's mother" can have a summary node annotation of "Mother(Father(Myself))"

Whether this argument was resolved from a pronoun mention in the query. Eg: [how old was obama when he became president]

One or more ChainIds from a ChainAnnotation whose "organization_mid" matches the MID. As of 2021-01 multiple chain_ids may be specified if the organization for MID controls multiple chains. See go/chains-lckp-robust-triggering for motivation.

Whether this argument was added by CloseAnswers in Postref. This bit is used to mark the corresponding interpretation/intent query as such by setting is_close_interpretation bit.

Entity location information (latitude/longitude) from freebase.

The confidence (in [0, 1]) that the annotation is a reference that implies another entity (e.g., "my hotel" in "navigate to my hotel" is a reference to an explicit hotel from the user's hotel reservations).

Signals about the media entity for this argument.

If the literal.obj_type of the argument value is ID (Entity), this represents the collection that the entity in this argument is a member of.

The usual semantic role associated with the signal from lightweight tokens attached to this argument span.

What added this argument.

If the literal.obj_type of the argument value is ID (Entity), this stores cluster scoring information for that entity, if the entity belongs to a cluster.

The QRef confidence score for an entity argument.

Whether this annotation was propagated as part of a Genie rewrite (go/genie-aqua).

Whether this argument was resolved through context from a previous query. Examples: obama -> "he" is resolved from the Obama entity starbucks -> Q2 is resolved from the list of shops

What added the argument value.

This represents which list entities index refers to.

If true, the value of the argument is populated with the default value specified by the system if the value can't be inferred from the input query. In IntentConfig case, the default value is specified by using IntentConfig.slot.default_value.

Experiment ID for experiments that were used to parse this FunctionCall. Empty indicates no experiments used.

If this slot was transformed from or could be transformed to a facet on a categorical, that information is stored here.

Whether this argument was annotated by nimble (go/nimble-annotator)

Whether the argument entity comes from a graphic symbol annotation. This is later used as a heuristic for poor web result quality.

Signals about what other entities this entity implies / is implied by. This is useful for grounding. Example: b/138388207: suppressing song intents if the artist entity doesn't link to the song title. This value specifies the order of annotations in a QRef annotation chain so they can refer to each other.

Contains the source and type information related to a personal entity, for example if it is a hotel or a restaurant (type) and if it comes from Gmail, Calendar, etc. (source).

Webref entity index for this argument, necessary for interpreting the relationship structure, and the list to index into. Specifically we need this to understand qref implications since they edges are represented with entity indexes.

Signals about what other entities this entity implies / is implied by. This is useful for grounding. Example: b/138388207: suppressing song intents if the artist entity doesn't link to the song title.

Signals derived from Munin Function call annotations.

Equivalent shopping ids for the argument.

How this argument was resolved through context from a previous query. Examples: obama -> "he" is resolved from the Obama entity starbucks -> Q2 is resolved from the list of shops (Attentional Entities)

Signals to facilitate orchestration of TUIG annotations.

Relationships between entities

The confidence (in [0, 1]) that the annotation was created on an implicit mention (e.g., "my hotel") as opposed to an explicit mention (e.g., "the westin copley square").

The list of result supports for this Argument.

If the argument is entity, the ungrounded type the entity is. For example, the entity argument is /m/0p83l (Jasmine), the value of this field should be "Plant" if it is present.

The oyster feature id. NOTE: As of Mar 2017, the cell ID field of the feature ID might not be set. See http://b/35447230#comment10

Information about where the value of this argument came from. For example, it could have been explicitly provided in the query, pulled in from the previous state, or pulled from attentional entities.

Whether the argument entity comes from a manual graphic symbol annotation. This is later used as a heuristic for poor web result quality.