RepositoryWebrefEntityJoin

Repository WebrefEntity Understanding

GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefEntityJoin

9
out of 10
Critical
SEO Impact
Next available tag: 35. Represents all the information that we have for a given entity.

SEO Analysis

AI Generated

Part of Google's entity understanding system (WebRef). This system identifies and links entities—people, places, things, concepts—within web content to Google's Knowledge Graph. Entity recognition is fundamental to semantic search, helping Google understand content meaning beyond keywords and match it to relevant queries.

Actionable Insights for SEOs

  • Monitor for changes in rankings that may correlate with updates to this system
  • Consider how your content strategy aligns with what this signal evaluates
  • Build topical authority through comprehensive, entity-focused content
  • Implement structured data to help Google understand entities on your pages
  • Create content that clearly establishes entity relationships

Attributes

12
Sort:|Filter:
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefWebrefEntityId.t

The id of this entity, prefer accessing through webref-entities-util.h functions.

Default: nilFull type: list(GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefSimplifiedCompositeDoc.t

This field contains reference pages for this entity. A reference page is a page that is highly topical for this entity, which can be used to mine additional information about this entity. Example reference pages for Apple Inc. would be the composite docs for "http://en.wikipedia.org/wiki/Apple_Inc." and http://www.apple.com. For actors or movies, you can also have the imdb page. Also see: http://go/refx-pages.

Default: nilFull type: list(GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefGlobalNameInfo.t

The context names (with scores) of this entity. The difference to regular names (aka name_info) is that context names are not used for finding mentions in a document as they consist of names somehow related to the entity (e.g. name "fisherman s wharf" for the entity "Gary Danko"). Used for reconciling freebase and oyster.

Default: nilFull type: list(GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefEntityDebugInfo.t

Debug information about the entity.

Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefAnnotatorProfile.t

Optional profiling data from the enricher that enriched this entity (and produced this EntityJoin as debug output).

Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefEnricherDebugData.t

Contains debug data produced by enricher and only used for debug purpose (e.g. demo).

Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefExtraMetadata.t

Additional metadata about the entity, that can be derived from the "raw data" (composite doc, domain specific data...), or come from other sources. Despite its name, this field often contains quite important information.

Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefHumanRatings.t

Human ratings (e.g. ratings from EWOK). This is typically only populated in the evaluation pipelines (e.g. P@5).

Default: nilFull type: list(GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefGlobalLinkInfo.t

Contains all links (with scores) that Webref knows for this entity. Links are relationships between entities. The data in this field is very important for the quality of the model.

Default: nilFull type: list(GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefGlobalNameInfo.t

Contains all names (with scores) that Webref knows for this entity. The data in this field is very important for the quality of the model.

Default: nilFull type: list(GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefRefconRefconNameInfo.t

Contains names and names metadata used by Refcon.

Default: nilFull type: list(GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefDomainSpecificRepresentation.t

An entity can have metadata from various data sources. Generally speaking all sources will be / should be reconciled into a single KG Topic entry. However, in some cases we pull in additional chunks of metadata from these sources; these are stored in this field. For example a local business could have a KG entry (topic proto), wikipedia entry (WikiJoin) and a MapFacts entry (Feature proto).