Real-Time Search Engine with Knowledge Graph Overlay

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current search engines lack the ability to efficiently predict outcomes and recommend content items in real-time based on detected events, as they rely on outdated methods that do not effectively utilize real-time data feeds and context analysis to update knowledge graphs and provide personalized recommendations.

Innovation Solution

A search engine system that includes a knowledge graph modification unit, scenario detection unit, query unit, scoring unit, and notification unit, which processes real-time data feeds to detect entities, update knowledge graphs, and generate event-outcome pairs, allowing for near real-time prediction and recommendation of content items based on historical relationships and user behavior.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If search engines use traditional keyword-based search and retrieval methods, then they can identify relevant search results based on search term frequency and metadata, but they lack the ability to predict outcomes and provide personalized recommendations in real-time

Engineering Contradiction:
Improvereal-time prediction and recommendation capabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system is divided into distinct functional modules: a knowledge graph modification unit for updating entity relationships, a scenario detection unit for identifying events, a query unit for processing search requests, a scoring unit for ranking results, and a notification unit for delivering recommendations. This segmentation allows each component to specialize in specific tasks, enabling real-time prediction capabilities without overwhelming system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system pre-processes and stores entity relationships, event scenarios, and historical data in knowledge graphs before search queries are submitted. By maintaining pre-computed event-outcome pairs and entity associations in structured knowledge graphs, the system can rapidly retrieve and apply this information during real-time search operations, enabling fast predictions without complex runtime computations.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If search engines process and analyze real-time data feeds to update knowledge graphs, then they can provide personalized recommendations, but this increases processing time and computational resources

Engineering Contradiction:
Improverecommendation accuracyVSAvoidprocessing latency
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system implements periodic batch processing of real-time data feeds to update knowledge graphs at scheduled intervals rather than continuously processing every incoming data point. This periodic approach maintains recommendation accuracy by regularly incorporating new information while avoiding the latency and resource consumption of continuous real-time processing for every search query.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system processes only the most relevant portions of real-time data feeds that directly impact search results and recommendation accuracy. By selectively filtering and processing only critical data elements rather than analyzing entire data feeds, the system achieves sufficient recommendation precision while minimizing processing time and computational resource usage.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If search engines maintain comprehensive knowledge graphs with historical relationships, then they can improve search relevance, but this increases data storage requirements and query complexity

Engineering Contradiction:
Improvesearch result relevanceVSAvoidknowledge graph management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts and stores only the most critical entity relationships, event scenarios, and outcome pairs from comprehensive knowledge graphs into optimized data structures. By selecting and retaining only the essential information needed for search relevance and prediction accuracy, the system maintains reliable search results while reducing knowledge graph management complexity and improving query processing efficiency.

Inventive Principle:
Principle #2Taking out (Extraction)

4Adaptability or versatility

If search engines use entity name identification and occurrence counting to determine relevance, then they can retrieve results based on entity frequency, but they cannot effectively predict outcomes or provide contextual recommendations

Engineering Contradiction:
Improvecontextual understanding and prediction capabilityVSAvoiddata structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system transitions from traditional single-dimensional keyword matching to multi-dimensional analysis by incorporating entity relationships, event contexts, historical outcomes, and user behavior patterns. This dimensional expansion enables contextual understanding and outcome prediction by analyzing search queries across multiple layers of information including entity associations, event scenarios, and temporal patterns, rather than relying solely on search term frequency.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentEP3577573B1Graphical user interface for displaying search engine results
Publication Date: 2022.01.05 KENSHO TECHNOLOGIES LLC
  • EP3577573B1 patent drawingFigure 1
  • EP3577573B1 patent drawingFigure 2
  • EP3577573B1 patent drawingFigure 3

AI summary

Methods, systems, apparatus, including computer programs encoded on computer storage medium, for generating rendering data. The method includes actions of receiving a stream of real-time data, analyzing the stream of real-time data to detect a set of one or more attributes associated with a real-time event, identifying, based on the one or more attributes, one or more data records representing an event-outcome pair, wherein an outcome in the event-outcome pair includes data identifying a content item, obtaining historical data associated with the content item, and generating rendering data including data for rendering a first layer representing real-time data specifying a current value of the content item as an overlay to a second layer representing the obtained historical data associated with the content item, with each of the rendered layers being juxtaposed to one or more specified portions of the graphical user interface.