A Knowledge Graph for the Agri-Food Sector

Written by Raul Palma on 29 January 2021. Posted in Use Cases

(Reading time: 7 - 13 minutes)

Raul Palma leads the data analytics and semantics department at the Poznan Supercomputing and Networking Center (PSNC), where he coordinates the R&D activities and the center’s participation in various EU projects around these topics. In this guest post for the metaphacts blog, Raul explains how knowledge graph technology can address data integration challenges in the agri-food sector, showcasing it through a few use cases. He describes how he leveraged metaphactory to build a domain-specific application - FOODIE - that delivers intuitive access to distributed, heterogeneous data sources and allows end users to extract meaningful insights.

FOODIE is an agriculture knowledge hub delivered as a Web application built on top of metaphactory Knowledge Graph platform. The application enables an integrated view and access over multiple datasets which have been collected from various and heterogeneous sources relevant to the agriculture sector, transformed, and published as Linked Data / in a Knowledge Graph.

Smart Solutions for Identifying Compatible Components - Powered by metaphactory and RDFox

Written by Irina Schmidt on 18 November 2020. Posted in Use Cases

(Reading time: 4 - 8 minutes)

Smart Solutions for Identifying Compatible Components

This article was co-written by Felicity Mulford (Oxford Semantic Technologies). Thank you to Valerio Cocchi (Oxford Semantic Technologies), and Ilija Kocev and Daniel Herzig (metaphacts) for their work on the demo system.

Determining compatibility between individual entities is an essential process for many businesses, across various industries and business models; from industrial configuration, supply chain, bill of materials, evaluating terms in contracts, or even for match making apps. The process may sometimes require the user to check hundreds of thousands or millions of possible combinations, to assess whether components fit together, or if components meet specified requirements. Additional factors may also need to be taken into account, for example, regulations or customer budgets. Traditional approaches are inefficient for modern day applications due to the large volumes of data, heterogeneity of data formats, complexity of customer specifications, and concerns over scalability.