CINXE.COM
KBpedia - Browse the Knowledge Graph
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <!--[if IE 8]> <html lang="en" class="ie8"> <![endif]--> <!--[if IE 9]> <html lang="en" class="ie9"> <![endif]--> <!--[if !IE]><!--> <html lang="en"> <!--<![endif]--> <head> <title>KBpedia - Browse the Knowledge Graph</title> <link rel="alternate" type="application/rss+xml" title="" href="/resources/feeds/news.xml" /> <!-- Meta --> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta name="description" content=""> <meta name="author" content=""> <!-- Favicon --> <link rel="shortcut icon" href="/favicon.ico"> <!-- CSS Global Compulsory --> <link rel="stylesheet" href="/assets/plugins/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/assets/css/style.css"> <!-- CSS Implementing Plugins --> <link rel="stylesheet" href="/assets/plugins/line-icons/line-icons.css"> <link rel="stylesheet" href="/assets/plugins/font-awesome/css/font-awesome.min.css"> <!-- CSS Theme --> <link rel="stylesheet" href="/assets/css/theme-colors/blue.css"> <link rel="stylesheet" href="/assets/css/footers/footer-v1.css"> <link rel="stylesheet" href="/assets/css/headers/header-v1.css"> <!-- CSS Customization --> <link rel="stylesheet" href="/css/custom.css"> <meta property="og:site_name" content="KBpedia"/> <meta property="og:title" content="Knowledge Graph Use Case: Browse the Knowledge Graph"> <meta property="og:type" content="article"/> <meta property="og:description" content="We describe how to browse the KBpedia knowledge graph"> <meta property="og:image" content="/imgs/kbpedia-logo-350.png"> <meta property="og:image:width" content="350"> <meta property="og:image:height" content="390"> </head> <body> <div class="wrapper"> <div class="header-v1"> <!-- Topbar --> <div class="topbar"> <div class="container"> <div class="col-md-1"> </div> <a class="navbar-brand" href="/"> <img id="logo-header" src="/imgs/kbpedia-logo-420-horz.png" height="75" alt="KBpedia Knowledge Structure" name="logo-header"> </a> </div> </div><!-- End Topbar --> <!-- Navbar --> <div class="navbar navbar-default mega-menu" role="navigation"> <div class="container"> <!-- Brand and toggle get grouped for better mobile display --> <div class="navbar-header"> <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-responsive-collapse"> <span class="sr-only">Toggle navigation</span> </button> </div> <div style="clear:both; height: 1px;"> </div> <!-- Collect the nav links, forms, and other content for toggling --> <div class="col-md-1"> </div><!--/col-md-1--> <div class="collapse navbar-collapse navbar-responsive-collapse col-md-10"> <ul class="nav navbar-nav pull-left"> <!-- Demo --> <li> <a href="/">Home</a> </li> <!-- Home --> <li> <a href="/knowledge-graph/">knowledge Graph</a> </li> <li> <a href="http://sparql.kbpedia.org/">SPARQL</a> </li> <!-- Background --> <li class="dropdown"> <a href="/background/">Background</a> <ul class="dropdown-menu"> <li> <a href="/background/overview/">Overview</a> </li> <li> <a href="/background/features-and-benefits/">Features & Benefits</a> </li> <li> <a href="/background/data-and-knowledge-structures/">Data and Knowledge Structures</a> </li> <li> <a href="/background/technology/">Technology</a> </li> <li> <a href="/background/machine-learning/">Machine Learning</a> </li> <li> <a href="/background/uses/">Uses</a> </li> </ul> </li><!-- End Uses --> <li class="dropdown"> <a href="/use-cases/">Use Cases</a> <ul class="dropdown-menu"> <li class="dropdown-submenu"> <a href="/use-cases/knowledge-graph/">Knowledge Graph (KG)</a> <ul class="dropdown-menu"> <li><a href="/use-cases/browse-the-knowledge-graph/">Browse the Knowledge Graph</a></li> <li><a href="/use-cases/search-the-knowledge-graph/">Search the Knowledge Graph</a></li> <li><a href="/use-cases/expand-queries-using-semsets/">Expand Queries Using Semsets</a></li> <li><a href="/use-cases/use-and-control-of-inferencing/">Uses and Control of Inferencing</a></li> </ul> </li> <li class="dropdown-submenu"> <a href="/use-cases/machine-learning-use-case/">Machine Learning (KBAI)</a> <ul class="dropdown-menu"> <li><a href="/use-cases/text-classification-using-esa-and-svm/">Create Supervised Learning Training Sets</a></li> <li><a href="/use-cases/document-specific-word2vec-training-corpuses/">Create Word Embedding Corpuses</a></li> <li><a href="/use-cases/extending-kbpedia-with-kbpedia-categories/">Create Graph Embedding Corpuses</a></li> <li><a href="/use-cases/text-classification-using-esa-and-svm/">Classify Text</a></li> <li><a href="/use-cases/dynamic-machine-learning/">Create 'Gold Standards' for Tuning Learners</a></li> <li><a href="/use-cases/disambiguating-kbpedia-knowledge-graph-concepts/">Disambiguate KG Concepts</a></li> <li><a href="/use-cases/dynamic-machine-learning/">Dynamic Machine Learning Using the KG</a></li> </ul> </li> <li class="dropdown-submenu"> <a href="/use-cases/mapping-use-case/">Mapping</a> <ul class="dropdown-menu"> <li><a href="/use-cases/mapping-external-data-and-schema/">Map Concepts</a></li> <li><a href="/use-cases/extending-kbpedia-with-kbpedia-categories/">Extend KBpedia with Wikipedia</a></li> <li><a href="/use-cases/benefits-from-extending-kbpedia-with-private-datasets/">Extend KBpedia for Domains</a></li> <li><a href="/use-cases/mapping-external-data-and-schema/">General Use of the Mapper</a></li> </ul> </li> </ul> </li> <li class="dropdown"> <a href="/resources/">Resources</a> <ul class="dropdown-menu"> <li><a href="/resources/downloads/">Download KBpedia</a></li> <li><a href="/resources/about/">About KBpedia</a></li> <li><a href="/resources/faq/">KBpedia FAQ</a></li> <li><a href="/resources/news/">News About KBpedia</a></li> <li><a href="/resources/statistics/">KBpedia Statistics</a></li> <li><a href="/resources/documentation/">Additional Documentation</a></li> <li><a href="/resources/support/">Support for KBpedia</a>.</li> </ul> </li> </ul> </div><!--/navbar-collapse--> <div class="col-md-1"> </div><!--/col-md-1--> </div> </div><!-- End Navbar --> </div><!--=== End Header ===--> <!--=== Breadcrumbs ===--> <div class="breadcrumbs"> <div class="container"> <div class="col-md-1"> </div><!--/col-md-1--> <div class="col-md-10"> <h1 class="pull-left"></h1> <ul class="pull-right breadcrumb"> <li>Use Cases</li> <li class="active">Browse the Knowledge Graph</li> </ul> </div><!--/col-md-10--> <div class="col-md-1"> </div><!--/col-md-1--> </div> </div> <!--/breadcrumbs--> <!--=== End Breadcrumbs ===--> <!--=== Content Part ===--> <div class="container content"> <div class="row"> <div class="col-md-2"> </div> <div class="col-md-8"> <div class="use-cases-header"> <table border="0" cellpadding="4" cellspacing="2"> <tbody> <tr> <td colspan="2" align="center"> <h2> <b>USE CASE</b> </h2> </td> </tr> <tr> <td style="width: 140px;" valign="top"> <b>Title:</b> </td> <td style="padding-left: 25px;" valign="top"> <span style="font-weight: bold;">Browsing the KBpedia Knowledge Graph</span> </td> </tr> <tr> <td valign="top"> <b>Short Description:</b> </td> <td style="padding-left: 25px;" valign="top"> We describe how to browse the KBpedia knowledge graph <br> </td> </tr> <tr> <td valign="top"> <b>Problem:</b> </td> <td style="padding-left: 25px;" valign="top"> We want to understand the coverage and linkages within a knowledge graph (also called an ontology) <br> </td> </tr> <tr> <td valign="top"> <b>Approach:</b> </td> <td style="padding-left: 25px;" valign="top"> KBpedia is a computable structure, logically coherent and structurally consistent. The <a href= "/knowledge-graph/">online knowledge graph</a> showcases many of these structural aspects -- concepts, entities, attributes, typologies and aspects -- and also supports direct and inferential browsing of the structure. This online example is not necessarily what may be used by specific clients. The first difference, of course, is that most clients need to expand or bridge off of KBpedia with their own domain schema and data. The second difference is that the look-and-feel and some functionality may be modified for specific uses. </td> </tr> <tr> <td valign="top"> <b>Key Findings:</b> </td> <td valign="top"> <p> The uses for browsing a knowledge graph include: </p> <ul> <li>Learning about individual concepts and entities </li> <li>Discovering related concepts and entities </li> <li>Understanding the structure and typologies of the knowledge graph </li> <li>Tracing conceptual lineages </li> <li>Exploring inferences based on the logical assertions in the graph </li> <li>General grazing and discovery, and many more, plus </li> <li>Parallel access to structured and semantic search. </li> </ul> <p> These uses do <span style= "font-weight: bold; font-style: italic;">not</span> include the work-related tasks in natural language processing or knowledge-based artificial intelligence discussed under other use cases. </p> </td> </tr> </tbody> </table> </div> </div> <div class="col-md-2"> </div><!--/col-md-2--> </div> <div class="row"> </div> <div class="row"> </div> <div class="row"> <div class="col-md-2"> </div> <div class="col-md-8"> <p> The example we present herein is based on the concept of ‘<a href= "/knowledge-graph/reference-concept/?uri=Currency">currency</a>‘, which you may interactively inspect for yourself <a href= "/knowledge-graph/reference-concept/?uri=Currency">online</a>. </p> <p> The KBpedia knowledge structure combines six major knowledge bases and maps to a further 20 other common vocabularies. KBpedia contains more than 53,000 reference concepts (RCs), organized into a knowledge graph as defined by the <a href= "/docs/kko-upper-structure">KBpedia Knowledge Ontology</a>. KKO is a logically organized and computable structure that supports inference and reasoning. </p> <p> About 85% of the RCs are themselves entity types — that is, 47,000 natural classes of similar entities such as astronauts or zoo animals — that are organized into about <a href= "/docs/30-typologies/">30 “core” typologies</a> that are mostly disjoint (non-overlapping) with one another. By definition an entity type is also a ‘reference concept’, or RC. </p> <p> KBpedia’s typologies provide a powerful means for slicing-and-dicing the knowledge structure. The individual entity types provide the tie-in points to about <a href= "/docs/kbpedia-statistics/">32 million individual entities</a>. The remaining RCs are devoted to other logical divisions of the knowledge graph, specifically attributes, relations and topics. It is this structure, plus often connections to another 20 leading external vocabularies, that forms the basis of the KBpedia Knowledge Graph. </p> <p> For the standard RC, each concept has a record with potentially eight (8) main panels or sections, each of which is described below: </p> <ul> <li>Header </li> <li>Core Structure </li> <li>Extended Linkages </li> <li>Typologies </li> <li>Entities </li> <li>Aspect-related Entities </li> <li>Broader Concepts </li> <li>Narrower Concepts. </li> </ul> <p> Panels are only displayed when there are results for them. </p> <br /> <h3> Header </h3> <p> Each entry begins with a header: </p> <center> <a href= "browse-kg-header.png"> <img alt="Header to Knowledge Graph Entry" title= "Header to Knowledge Graph Entry" src= "browse-kg-header.png" data-lazy-src= "browse-kg-header.png" class="lazyloaded" align="middle"></a> </center> <br /> <p> Above the header to the left is the listing for the current KBpedia version and its date of release. Next to it is a link for sending an email to a graph administrator should there be a problem with the current entry. Above the header to the right is the search box, itself the topic of another application case. </p> <p> The Header consists of these possible entries: </p> <ul> <li> <b>prefLabel</b> – <b>URI</b> – <b>image</b> — the prefLabel is the name or “title” for the RC. While the name has no significant meaning in and of itself (the <i>meaning</i> for the RC is a result of all specifications and definitions, including relations to other objects, for the concept), the prefLabel does provide a useful shorthand or handle for referring to the concept. The URI is the full Web reference to the concept, such as <small><code><a href= "http://kbpedia.org/kko/rc/Currency">http://kbpedia.org/kko/rc/Currency</a></code></small>. If there is an image for the RC, it is also displayed </li> <li> <b>semset</b> — the entries here, also known as altLabels, are meant to inclusively capture all roughly equivalent references to the concept, including synonyms, slang, jargon and acronyms </li> <li> <b>definition</b> — the readable text definition or description of the RC; some live links may be found in the definition. </li> </ul> <br /> <h3> Core Structure </h3> <p> The Core Structure for KBpedia is the next panel. Two characteristics define what is a core contributor to the KBpedia structure: 1) the scale and completeness of the source; and 2) its contribution of a large number of RCs to the overall KKO knowledge graph. The KBs in the core structure play a central role in the scope and definition of KBpedia. This core structure of KBpedia is supplemented by mappings to about 20 additional external linkages, which are highly useful for interoperability purposes, but do not themselves contribute as much to the RC scope of the KKO graph. The Core Structure is derived from the six (6) main knowledge bases — <a href="https://en.wikipedia.org/wiki/Wikipedia">Wikipedia</a>, <a href="https://en.wikipedia.org/wiki/Wikidata">Wikidata</a>, <a href="https://schema.org/">schema.org</a>, <a href="http://dbpedia.org/">DBpedia</a>, <a href="https://en.wikipedia.org/wiki/GeoNames">GeoNames</a>, and <a href="https://en.wikipedia.org/wiki/Cyc">OpenCyc</a>. </p> <p> The conceptual relationships in the KBpedia Knowledge Ontology (KKO) are largely drawn from OpenCyc, UMBEL, or Wikipedia, though any of the other sources may contribute local knowledge graph structure. Additional reference concepts are contributed primarily from GeoNames. Wikidata contributes the bulk of the instance data, though instance records are actually drawn from all sources. DBpedia and Wikidata are also the primary sources for attribute characterizations of the instances. Instance data, by definition, are <em><strong>not</strong></em> part of the core structure. </p> <p> Here is the Core Structure panel: </p> <center> <a href= "browse-kg-core.png"> <img alt="Core Structure for a Knowledge Graph Entry" title= "Core Structure for a Knowledge Graph Entry" src= "browse-kg-core.png" data-lazy-src= "browse-kg-core.png" class="lazyloaded" align="middle"></a> </center> <br /> <p> The Core Structure panel, like the other panels, has a panel title followed by a brief description. The Core Structure panel lists the equivalent class (<code>owl:equivalentClass</code>), parent super classes (<code>kko:superClassOf</code>), child sub classes (<code>rdfs:subClassOf</code>), or a closely related concept (<code>kko:isCloselyRelated</code>) (not shown). These relationships define the edges between the nodes in the graph structure, and are also the basis for logical inferencing. </p> <p> Sub-classes and super-classes may be determined either as <i>direct</i> assertions or those that are <i>inferred</i> from parent-child relationships in the Knowledge Graph. An <span>inferred</span> relationship includes any of the parent or child ancestors; the <span>direct</span> is the immediate child or parent. Picking one of these links restricts the display to the concepts related to that category. Like familial relationships, the closer the concept is to its lineage relation, the likely closer are the shared attributes or characteristics of the concepts. Such lineage inferences arise from the relations in the KBpedia Knowledge Ontology (KKO). </p> <p> Each of the related concepts is presented as a live link, which if clicked, will take you to a new entry for that concept. Some of the icons and information for equivalent classes are discussed under other panels below. </p> <br /> <h3> External Linkages </h3> <p> In addition to the Core Structure, KBpedia RCs are linked to thousands of classes defined in nearly <a href= "/docs/extended-mappings/">20 external ontologies</a> used to describe all kinds of public and private datasets. Some of the prominent external vocabularies include schema.org, the major structured data system for search engines, and Dublin Core, a key vocabulary from the library community. Other external vocabularies cover music, organizations, projects, social media, and the like. </p> <p> Here is how the External Linkages panel looks, which has many parallels to the Core Structure panel: </p> <center> <a href= "browse-kg-external.png"> <img alt="External Linkages for a Knowledge Graph Entry" title= "External Linkages for a Knowledge Graph Entry" src= "browse-kg-external.png" data-lazy-src= "browse-kg-external.png" class="lazyloaded" align="middle"></a> </center> <br /> <p> </p> <p> The external links, like the core ones, are shown as live links with an icon associated to each source. For RCs that are entity types, the entry might also display the count of entities (<span style= "color: rgb(255, 102, 0);">orange</span> background with count) or related-aspect entities (<span style= "color: rgb(51, 102, 255);">blue</span> background with count) linked to that RC (either directly or inferred, depending on the option chosen). Clicking on the specific RC link will take you to that reference concept. Clicking on the highlighted background will take you to a listing of the entities for that RC (based on either its direct or inferred option). </p> <p> Also, like the short descriptions on each of these panels, clicking the <span style="color: rgb(0, 204, 255);">more</span> link expands the description available: </p> <center> <a href= "browse-kg-external-more.png"> <img alt="Getting More Information" title="Getting More Information" src= "browse-kg-external-more.png" data-lazy-src= "browse-kg-external-more.png" class="lazyloaded" align="middle"></a> </center> <br /> <h3> Entities </h3> <p> Entities are distinct, nameable, individual things. There are more than 30 million of them in the baseline KBpedia. </p> <p> Entities may be physical objects or conceptual works or discrete ideas, so long as they may be characterized by attributes shared by other instances within similar kinds or types. Entities may be parts of other things, so long as they have a distinct identity and character. Entities with shared attributes that are the essences of the things may be grouped into natural types, called <i><b>entity types</b></i>. These entity types may be further related to other entity types in natural groupings or hierarchies depending on the attributes and their essences that are shared among them. </p> <p> Here is how the general Entities panel appears: </p> <center> <a href= "browse-kg-entities.png"> <img alt="Entities for a Knowledge Graph Entry" title= "Entities for a Knowledge Graph Entry" src= "browse-kg-entities.png" data-lazy-src= "browse-kg-entities.png" class="lazyloaded" align="middle"></a> </center> <br /> <p> In this case for <a href= "/knowledge-graph/reference-concept/?uri=Currency">currency</a>, there are 2003 instances (individual entities) in the current KBpedia knowledge base. The first few of these are shown in the panel, with the live links then taking you to the an entity report for that instance. Similarly, you can click the <em><strong>Browse all entities</strong></em> button, which then allows you to scroll through the entire listing of entities. Here is how that subsidiary page, in part, appears: </p> <center> <a href= "browse-kg-entities-detail.png"> <img alt="Entities Listing for a Knowledge Graph Entry" title= "Entities Listing for a Knowledge Graph Entry" src= "browse-kg-entities-detail.png" data-lazy-src= "browse-kg-entities-detail.png" class="lazyloaded" align="middle"></a> </center> <br /> <p> Nearly 85%, or 47,000, of the reference concepts within the KBpedia Knowledge Ontology (KKO) are entity types, these natural classes of entities. They are key leverage points for inteoperability and mapping. Instances (or entities) are related to the KKO graph via the <code>rdfs:type</code> predicate, which assigns an entity to one or more parental classes. It is through this link that you view the individual entities. </p> <br /> <h3> Aspect-related Entities </h3> <p> Entities may also be characterized according to one or more of about <a href="/docs/80-aspects">80 <b>aspects</b></a>. Aspects help to group related entities by situation, and not by identity nor definition. Aspects thus provide a secondary means for organizing entities independent of their nature, but helpful for placing the entity in real-world contexts. Not all aspects relate to a given entity. </p> <p> The Aspects panel has a similar presentation to the other panels: </p> <center> <a href= "browse-kg-aspects.png"> <img alt="Aspects for a Knowledge Graph Entry" title= "Aspects for a Knowledge Graph Entry" src= "browse-kg-aspects.png" data-lazy-src= "browse-kg-aspects.png" class="lazyloaded" align="middle"></a> </center> <br /> <p> If an entity with a related aspect occurs in the knowledge system, its aspect label will be shown with then a listing of the top entities for that aspect. Each of these entities is clickable, which will take you to the standard entity record. A button to <em><strong>Browse all entities</strong></em> means there are more entities for that aspect than the short listing will allow; click on it to be able to paginate through the full listing of related entities. </p> <p> Note, as well, on this panel that we are also highlighting the down arrow at the upper right of the panel. Clicking that causes the entire panel to collapse, leaving only the title. Clicking on the arrow again causes the panel to expand. This convention applies to all of the panels discussed here. </p> <br /> <h3> Typologies </h3> <p> About 85% of all of the reference concepts (RCs) in KBpedia represent classes of entities, which themselves are organized into about <a href= "/docs/30-typologies/">30 <i><b>core typologies</b></i></a>. Most of these typologies are disjoint (lack overlap) from one another, which provides an efficient mechanism for testing subsets and filtering entities into smaller groups for computational purposes. (Another 30 or so SuperTypes provide <span>extended</span> organization of these entities.) </p> <p> The Typologies panel follows some of the standard design of the other panels. Only the typologies to which the current entry belongs, in this case <a href= "/knowledge-graph/reference-concept/?uri=Currency">currency</a>, are shown: </p> <center> <a href= "browse-kg-typologies.png"> <img alt="Typologies for a Knowledge Graph Entry" title= "Typologies for a Knowledge Graph Entry" src= "browse-kg-typologies.png" data-lazy-src= "browse-kg-typologies.png" class="lazyloaded" align="middle"></a> </center> <br /> <p> As noted, the major groupings of types reside in <em><strong>core</strong></em> typologies, which is where the largest degree of disjointedness occurs. There are some upper typologies (such as <code>Living Things</code> over <code>Plants</code>, <code>Animals</code>, etc.) that are used mostly for organizational purposes; these are the <em><strong>extended</strong></em> ones. The core typologies are the key ones to focus upon for distinguishing large groupings of entities. </p> <br /> <h3> Concept Hierarchies </h3> <p> The last panel section for a concept presents both the parental (<em><strong>Broader</strong></em>) and child (<em><strong>Narrower</strong></em>) concepts for the current entry (again, in this case, <a href= "/knowledge-graph/reference-concept/?uri=Currency">currency</a>). <em><strong>Broader</strong></em> concepts represent the parents (or grandparental lineage in the case of inference) for the current reference concept. The broader concept relationship is expressed using the transitive <code>kko:superClassOf</code> property. This property is the inverse of the <code>rdfs:subClassOf</code> property. <em><strong>Narrower</strong></em> concepts represent the children (or grandchild lineages in the case of inference) for the current RC. The narrower concept relationship is expressed using the transitive <code>rdfs:subClassOf</code> property. This property is the inverse of the <code>kko:superClassOf</code> property. </p> <p> Here is the side-by-side panel presentation for these relationships: </p> <center> <a href= "browse-kg-hierarchy.png"> <img alt="Broader and Narrower Classes for a Knowledge Graph Entry" title="Broader and Narrower Classes for a Knowledge Graph Entry" src= "browse-kg-hierarchy.png" data-lazy-src= "browse-kg-hierarchy.png" class="lazyloaded" align="middle"></a> </center> <br /> <p> Like some of the prior panels, it is possible to toggle between direct and inferred listings of these related concepts. If the RC is an entity type, it may also show counts for all entities subsumed under that type (<span style="color: rgb(255, 102, 0);">orange</span> color) or that have aspects of that type (<span style= "color: rgb(51, 102, 255);">blue</span> color). Clicking on these count icons will take you to a listing of these entities. </p> <br /> <h3> Client Variations </h3> <p> This browsing and discovery use case is based on the standard configuration and the baseline KBpedia. Client variants may change the design and functionality of the application. More importantly, however, client applications are invariably extensions to the base KBpedia knowledge structure. These sometimes have some typologies removed because they are not relevant, but more likely have been expanded with the mapping of domain schema, vocabularies, and instances. In these cases, the actual content to be browsed may differ significantly from what is shown. </p> </div> <div class="col-md-2"> </div><!--/col-md-2--> </div> </div><!--/container--> <!--=== End Content Part ===--> <div class="footer-v1"> <div class="footer"> <div class="container"> <div class="row"> <!-- About --> <div class="col-md-3 md-margin-bottom-40"> <table> <tbody><tr> <td> <a href="/"> <img id="logo-footer" class="footer-logo" src="/imgs/logo-simple-purple.png" alt="" name="logo-footer"> </a> </td> </tr> <tr> <td> <center> <p> KBpedia </p> </center> </td> </tr> </tbody></table> <p style="font-size: 0.85em;"> KBpedia exploits large-scale knowledge bases and semantic technologies for machine learning, data interoperability and mapping, and fact extraction and tagging. </p> </div><!--/col-md-3--> <!-- End About --> <!-- Latest --> <div class="col-md-3 md-margin-bottom-40"> <div class="posts"> <div class="headline"> <h2> Latest News </h2> </div> <ul class="list-unstyled latest-list"> <!-- HTML generated from an RSS Feed by rss2html.php, http://www.FeedForAll.com/ a NotePage, Inc. product (http://www.notepage.com/) --> <li> <a href="https://kbpedia.org/resources/news/kbpedia-adds-ecommerce/">KBpedia Adds Major eCommerce Capabilities</a> <small>06/15/2020</small> </li> <!-- HTML generated from an RSS Feed by rss2html.php, http://www.FeedForAll.com/ a NotePage, Inc. product (http://www.notepage.com/) --> <li> <a href="http://kbpedia.org/resources/news/kbpedia-continues-quality-improvements/">KBpedia Continues Quality Improvements</a> <small>12/04/2019</small> </li> <!-- HTML generated from an RSS Feed by rss2html.php, http://www.FeedForAll.com/ a NotePage, Inc. product (http://www.notepage.com/) --> <li> <a href="http://kbpedia.org/resources/news/wikidata-coverage-nearly-complete/">Wikidata Coverage Nearly Complete (98%)</a> <small>04/08/2019</small> </li> </ul> </div> </div><!--/col-md-3--><!-- End Latest --><!-- Link List --> <div class="col-md-3 md-margin-bottom-40"> <div class="headline"> <h2> Other Resources </h2> </div> <ul class="list-unstyled link-list"> <li> <a href="/resources/about/">About</a> </li> <li> <a href="/resources/faq/">FAQ</a> </li> <li> <a href="/resources/news/">News</a> </li> <li> <a href="/use-cases/">Use Cases</a> </li> <li> <a href="/resources/documentation/">Documentation</a> </li> <li> <a href="/resources/privacy/">Privacy</a> </li> <li> <a href="/resources/terms-of-use/">Terms of Use</a> </li> </ul> </div><!--/col-md-3--> <!-- End Link List --><!-- Address --> <div class="col-md-3 map-img md-margin-bottom-40"> <div class="headline"> <h2> Contact Us </h2> </div> <address class="md-margin-bottom-40"> c/o <a href="mailto:info@mkbergman.com?subject=KBpedia%20Inquiry">Michael K. Bergman</a> <br> 380 Knowling Drive <br> Coralville, IA 52241 <br> U.S.A. <br> Voice: +1 319 621 5225 </address> </div><!--/col-md-3--> <!-- End Address --> </div> </div> </div><!--/footer--> <div class="copyright"> <div class="container"> <div class="row"> <div class="col-md-7"> <p class="copyright" style="font-size: 10px;"> 2016-2022 © <a href="http://kbpedia.org" style="font-size: 10px;">Michael K. Bergman.</a> All Rights Reserved. </p> </div> <!-- Social Links --> <div class="col-md-5"> <ul class="footer-socials list-inline"> <li> <a href="/resources/feeds/news.xml" class="tooltips" data-toggle="tooltip" data-placement="top" title="" data-original-title="RSS feed"> <i class="fa fa-rss-square"></i> </a> <br></li> <li> <a href="http://github.com/Cognonto" class="tooltips" data-toggle="tooltip" data-placement="top" title="" data-original-title="Github"> <i class="fa fa-github"></i> </a> <br></li> <li> <a href="http://twitter.com/cognonto" class="tooltips" data-toggle="tooltip" data-placement="top" title="" data-original-title="Twitter"> <i class="fa fa-twitter"></i> </a> <br></li> </ul> </div> <!-- End Social Links --> </div> </div> </div><!--/copyright--> </div><!--=== End Footer Version 1 ===--> <!--/wrapper--> <!-- JS Global Compulsory --> <script type="text/javascript" src="/assets/plugins/jquery/jquery.min.js"></script> <script type="text/javascript" src="/assets/plugins/jquery/jquery-migrate.min.js"></script> <script type="text/javascript" src="/assets/plugins/bootstrap/js/bootstrap.min.js"></script> <!-- JS Implementing Plugins --> <script type="text/javascript" src="/assets/plugins/back-to-top.js"></script> <!-- JS Customization --> <script type="text/javascript" src="/assets/js/custom.js"></script> <!-- JS Page Level --> <script type="text/javascript" src="/assets/js/app.js"></script> <!-- JS Implementing Plugins --> <script type="text/javascript" src="/assets/plugins/smoothScroll.js"></script> <script type="text/javascript" src="/assets/plugins/owl-carousel/owl-carousel/owl.carousel.js"></script> <script type="text/javascript" src="/assets/plugins/layer-slider/layerslider/js/greensock.js"></script> <script type="text/javascript" src="/assets/plugins/layer-slider/layerslider/js/layerslider.transitions.js"></script> <script type="text/javascript" src="/assets/plugins/layer-slider/layerslider/js/layerslider.kreaturamedia.jquery.js"></script> <!-- JS Customization --> <script type="text/javascript" src="/assets/js/custom.js"></script> <!-- JS Page Level --> <script type="text/javascript" src="/assets/js/plugins/layer-slider.js"></script> <script type="text/javascript" src="/assets/js/plugins/style-switcher.js"></script> <script type="text/javascript" src="/assets/js/plugins/owl-carousel.js"></script> <script type="text/javascript" src="/assets/js/plugins/owl-recent-works.js"></script> <script type="text/javascript"> jQuery(document).ready(function() { App.init(); LayerSlider.initLayerSlider(); StyleSwitcher.initStyleSwitcher(); OwlCarousel.initOwlCarousel(); OwlRecentWorks.initOwlRecentWorksV2(); }); </script> <!--[if lt IE 9]> <script src="assets/plugins/respond.js"></script> <script src="assets/plugins/html5shiv.js"></script> <script src="assets/plugins/placeholder-IE-fixes.js"></script> <![endif]--> <!--[if lt IE 9]> <script src="/assets/plugins/respond.js"></script> <script src="/assets/plugins/html5shiv.js"></script> <script src="/assets/js/plugins/placeholder-IE-fixes.js"></script> <![endif]--> <script> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','https://www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-84405507-1', 'auto'); ga('send', 'pageview'); </script>