Ontology-Based Data Repository Querying for Multi-Dataset Views

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large-scale data analytic systems face challenges with increased dataset size leading to performance degradation and user interaction difficulties with multi-dataset repositories.

Innovation Solution

A method and system that generate searchable databases from datasets in a data repository using ontological data, allowing for the creation of object views that are displayed based on defined ontological data, facilitating user interaction and dataset management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If relational data is stored within datasets themselves, then data structure completeness is improved, but dataset size increases and system performance deteriorates

Engineering Contradiction:
Improvedata structure completenessVSAvoidsystem performance
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The patent segments relational data into two parts: core dataset content and relational structure. The relational data is extracted and stored separately as an ontology model, while the datasets retain only essential data. This segmentation reduces dataset size and improves performance while maintaining data structure completeness through the separate ontology layer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an ontology layer as an intermediary between datasets and users. This ontology acts as a mediator that manages relational data independently, allowing datasets to remain lightweight while the ontology handles complex relationships. The ontology serves as the intermediary structure that maintains data completeness without burdening the datasets themselves.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Quantity of substance

If multiple datasets are stored in a data repository, then data comprehensiveness is improved, but user interaction difficulty increases

Engineering Contradiction:
Improvedata comprehensivenessVSAvoiduser interaction ease
Core Design Contradiction:
Quantity of substanceVSEase of operation

Solution Approach 1:

The patent creates a universal ontology layer that serves multiple datasets simultaneously. This single ontology structure provides multi-functional capabilities by managing relationships across all datasets in the repository. Users interact with this universal ontology rather than individual datasets, simplifying interaction while maintaining access to comprehensive multi-dataset information.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The ontology layer serves as an intermediary between users and multiple datasets. Instead of users directly navigating complex multi-dataset relationships, the ontology mediates by providing a unified view and managing relationships transparently. This intermediary layer simplifies user interaction while preserving access to comprehensive data across all datasets.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If datasets are joined using ontological data, then query accuracy is improved, but processing complexity increases

Engineering Contradiction:
Improvequery accuracyVSAvoidprocessing complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the processing complexity by separating ontology operations from dataset operations. Joining operations work with the structured ontology layer rather than raw datasets, which simplifies the joining logic. The ontology provides pre-defined relationship structures that improve query accuracy while containing processing complexity within the ontology management layer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter representation by using standardized ontology parameters instead of raw dataset parameters for joining operations. This parameter transformation allows for more accurate and consistent joins across datasets, as the ontology provides a unified parameter framework. The complexity is managed by working with standardized ontology parameters rather than heterogeneous dataset parameters.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250291851A1System and method for querying a data repository
Publication Date: 2025.09.18 PALANTIR TECHNOLOGIES INC
  • US20250291851A1 patent drawing
  • US20250291851A1 patent drawing
  • US20250291851A1 patent drawing

AI summary

A search request relating to one or more datasets in the data repository can be received, the search request comprising a display request to display at least a portion of the one or more datasets. In response to the search request, a searchable database can be generated from the one or more datasets in a data repository based on ontological data associated with the one or more datasets. An object view of at least the portion of one or more datasets can be generated from the searchable database, the view being generated based on the ontological data. The generated object view can be provided to be displayed on a display device.