Knowledge Graph Translation for Consistent Supply Chain Relationships

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing spreadsheet systems for managing linkages between service providers, receivers, and component providers are prone to human error, data inconsistency, and lack scalability and visualization tools, making it difficult to navigate complex relationships and extract meaningful insights.

Innovation Solution

A knowledge graph system is employed to semantically link and analyze data, using a semantic ontology to manage relationships between legal entities, with a knowledge graph application server that includes components for data ingestion, processing, and visualization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If spreadsheet systems are used to manage linkages between service providers, receivers, and component providers, then data can be stored and accessed, but human error, data inconsistency, and lack of scalability occur

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a knowledge graph system as an intermediary layer between data storage and user interaction. This knowledge graph automatically infers relationships, validates data consistency, and provides structured querying capabilities, thereby improving reliability without requiring complex manual spreadsheet management

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces manual spreadsheet operations with automated knowledge graph processing. The system automatically infers relationships, validates data, and provides visualization tools, eliminating human error and inconsistency associated with manual spreadsheet management

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Loss of information

If spreadsheet systems are used to track service relationships, then basic data storage is achieved, but navigation and visualization of complex relationships become difficult

Engineering Contradiction:
Improverelationship insightsVSAvoiddata navigation
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent transforms flat spreadsheet data into multi-dimensional knowledge graph structures. The system provides visualizations including entity relationship graphs, hierarchical views, and interactive explorations that reveal complex relationships across multiple dimensions, making navigation and insight extraction straightforward

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

Solution Approach 2:

The system provides automated feedback through relationship inference and validation. The knowledge graph continuously analyzes data relationships, identifies patterns, and presents insights back to users through visualizations and queries, eliminating the need for manual analysis

Inventive Principle:
Principle #23Feedback

3Productivity

If manual spreadsheet management is used, then implementation is simple, but scalability and accuracy deteriorate with increasing data volume

Engineering Contradiction:
Improvedata processing efficiencyVSAvoiddata accuracy
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The knowledge graph system performs self-service by automatically inferring relationships, validating data consistency, and generating insights without human intervention. The system scales efficiently by automatically processing increasing data volumes while maintaining or improving accuracy through automated validation rules

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12353351B2Systems and methods for data translation of source data files
Publication Date: 2025.07.08 WELLS FARGO BANK NA
  • US12353351B2 patent drawing
  • US12353351B2 patent drawing
  • US12353351B2 patent drawing

AI summary

A method may include accessing, using a processing unit, a source chain datafile formatted in a first format, the source chain datafile including data entries identifying linkages between a service provider, a service receiver, and a component provider, of an enterprise; forming, using the processing unit, initial knowledge graph tuples including subject, object, and predicate components based on the linkages; generating, using the processing unit, a staging knowledge graph storing the initial knowledge graph tuples; translating, using the processing unit, the initial knowledge graph tuples into production knowledge graph tuples according to a source chain knowledge graph schema; and storing, using the processing unit, the production knowledge graph tuples in a production knowledge graph.