Corpus-Scoped Annotation Analysis via Relational Database
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Typical cognitive computing environments face challenges in analyzing and searching annotations across an entire corpus due to their document-centric approach, which limits the ability to determine relationships and trends, and requires inefficient analysis of each document set, lacking the necessary detail for queries like identifying frequently occurring concepts.
Innovation Solution
Implementing a relational database to store content, metadata, and annotations in a normalized manner, enabling comprehensive corpus-scoped annotation and analysis by generating enrichment analysis data, which includes annotations and metadata for a plurality of documents, and using this data to resolve queries initiated by applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a document-centric approach is used to store and analyze annotations, then the system maintains simplicity in data organization, but it becomes inefficient for corpus-scoped analysis and cannot effectively identify relationships and trends across the entire corpus
Solution Approach 1:
The patent segments the annotation data into two distinct storage components: a traditional document-centric storage system for individual document annotations, and a new corpus-scoped storage system using relational databases for cross-document analysis. This segmentation allows each system to specialize - the document-centric system maintains simplicity while the corpus-scoped system enables efficient trend analysis across the entire corpus.
Solution Approach 2:
The patent adds a new dimension to data storage by introducing corpus-scoped metadata that transcends individual document boundaries. Instead of only storing annotations within their parent documents, the system creates a second dimension of organization where annotations can be queried and analyzed across the entire corpus, enabling identification of relationships and trends that span multiple documents.
2Quantity of substance
If annotations are stored at document granularity only, then storage requirements are reduced, but the ability to perform corpus-scoped queries and identify frequently occurring concepts is lost
Solution Approach 1:
The patent extracts essential annotation information from the full document annotations and stores it in a separate corpus-scoped metadata storage system. This extraction process selects only the most relevant features and characteristics of annotations that are useful for corpus-wide analysis, storing them in a normalized format that enables efficient querying while avoiding the need to store complete annotation details for every document.
Solution Approach 2:
The patent performs preliminary processing of annotation data during the annotation creation phase, pre-computing and storing corpus-scoped metadata that will be useful for future queries. This preliminary action includes normalizing annotation formats, extracting key features, and organizing data in a manner optimized for corpus-scoped analysis, so that when queries are executed, the system can quickly retrieve and analyze the pre-processed information without performing complex computations in real-time.
3Measurement precision
If each document set is analyzed individually, then analysis precision for individual documents is maintained, but overall productivity for corpus analysis decreases and time consumption increases
Solution Approach 1:
The patent merges individual document analysis results with corpus-scoped analysis by creating a unified query system that can operate at both levels. The system combines the precision of individual document analysis with the efficiency of corpus-wide processing through normalized metadata storage, allowing queries to simultaneously leverage detailed document-level information and aggregated corpus-level patterns without requiring separate analysis passes.
Data Source
AI summary
Corpus-scoped annotation and analysis. Enrichment analysis data is generated including annotations and metadata for a plurality of documents that are part of a corpus. Whether to generate a second set of annotations is determined, based on a correlation of the annotations and metadata. A relational database is populated with the enrichment analysis data. A corpus-scoped query is resolved, initiated by an application, using the enrichment analysis data and content of the corpus.


