Creating Meaning Schemas with Intent Lab

A defined structure representing a specific meaning or understanding, used for query processing.

A tool for creating and managing Meaning Schemas.

The Intent Lab tool where new Meaning Schemas are built. Used for creating schemas and properties.

A required environment in Intent Lab to create a Meaning Schema.

The standard way intents are triggered in a search, enabled in Intent Lab for Meaning Schemas.

A necessary addition to Loose Parsing for Meaning Schemas that optimizes search.

The section in Intent Lab that manages approval for a Meaning Schema submission.

A pre-existing list of Meaning Schemas to reuse or modify. Used to accelerate creation.

A voting method where no responses are provided, often used in technical situations like RiO fulfillment.

A side-by-side evaluation comparing wins and losses for a decision to enable answerless voting.

A document section containing information about the workspace, including rationale for answerless voting.

Placeholders in a Meaning Schema for handling undefined queries, including locations, dates, and numbers.

Knowledge Graph collections used for defining slots; specifically used for defining slots.

Slots in a Meaning Schema that must be filled versus the ones that can be omitted.

Examples of queries used to test and identify patterns that match a Meaning Schema, crucial data.

Tool for adding patterns to match Meaning Schema used in search stacks(for search engine optimization).

Adding patterns to a Meaning Schema involves specifying example query resolutions, like "New York" for a location slot. Patterns are added individually or in bulk, and separated by lines.

Marking a pattern as 'good' adds it to your Meaning Schema's search stack. Marking a pattern as 'bad' blocks it.

A tool that suggests patterns based on previously marked good/bad patterns. It uses loose parsing to predict related queries.

Important keywords used to improve Google's ranking algorithm (KScorer).

Checks to ensure changes don't negatively impact search results. Requires running evals (KE Evals, SxS) before changes are live.

Marking a pattern with this tag causes it to trigger the search stack.

The process of submitting a Meaning Schema for approval by a reviewer, initiating a review cycle.

Comments and suggestions provided by the reviewer after examining the submitted Meaning Schema.

The final step in the Meaning Schema approval process, after reviewer feedback is handled.

Automated checks performed before submitting a Meaning Schema, ensuring basic requirements are met.

The process of making changes to a Meaning Schema accessible to users, dependent on various binaries' releases.

An evaluation that compares side-by-side the results of a search with and without a Meaning Schema. It helps understand the potential impact of the schema on search results.

A regression test used to ensure that a new Meaning Schema doesn't negatively affect existing search functions.

An evaluation that tests how a new Meaning Schema affects the workload on the search system. It ensures that the new schema doesn't create excessive load during annotation phases.

A process where the changes made within a Workspace for a new Meaning Schema are reviewed and analyzed to assess their quality and potential impact.

Keywords attached to a Workspace Description that provide important information about the Meaning Schema project, like its impact, approval status, and testing results.

Submitting a completed Meaning Schema project to the appropriate person for approval, usually the owner of the relevant Management Area.