SIOC Post profile for "AI3:::Adaptive Information"
type: Document
description: A SIOC profile describes the structure and contents of a weblog in a machine readable form. For more information please refer to http://sioc-project.org/.
primary topic: CWPK #28: Extracting Structure for Typologies
generator agent: http://rdfs.org/sioc/wp-sioc.php

CWPK #28: Extracting Structure for Typologies
type: Post
has container: weblog
has creator: Mike Bergman
maker: Mike Bergman
created: 2020-09-02T15:22:17Z
content: We Extract a Typology Scaffolding from an Active KG In this installment of the Cooking with Python and KBpedia series, we work out in a Python code block how to extract a single typology from the KBpedia knowledge graph. To refresh your memory, KBpedia has an upper, 'core' ontology, the KBpedia Knowledge Ontology (KKO) that has a bit fewer than 200 top-level concepts. About half of these concepts are connecting points we call 'SuperTypes', that also function as tie-in points to underlying tree structures of reference concepts (RCs). (Remember there are about 58,000 RCs across all of KBpedia.) We call each tree structure a 'typology', which has a root concept that is one of the upper SuperType concepts. The tree structures in each typology are built from rdfs:subClassOf relations, also known as 'is-a'. The typologies range in size from a few hundred RCs to multiple thousands in some cases. The combination of the upper KKO structure and its supporting 70 or so typologies provide the conceptual backbone to KBpedia. We discussed this general terminology in our earlier CWPK #18 installment. Each typology extracted from KBpedia can be inspected as a standalone ontology in something like the Protégé IDE. Typologies can be created or modified offline and then imported back into KBpedia, steps we will address in later installments. The individual typologies are modular in nature, and a bit easier to inspect and maintain when dealt with independently of the entire KBpedia structure. Starting and Load We begin with our standard opening routine, though we are a bit more specific about identifying prefixes in our name spaces: Which environment? The specific load routine you should choose below depends on whether you are using the online MyBinder service (the 'raw' version) or local files. The example below is based on using local files (though replace with your own local directory specification). If loading from MyBinder, replace with the lines that are commented (#) out. main =…
encoded: We Extract a Typology Scaffolding from an Active KG In this installment of the Cooking with Python and KBpedia series, we work out in a Python code block how to extract a single typology from the KBpedia knowledge graph. To refresh your memory, KBpedia has an upper, ‘core’ ontology, the KBpedia Knowledge Ontology (KKO) that has a bit fewer than 200 top-level concepts. About half of these concepts are connecting points we call ‘SuperTypes’, that also function as tie-in points to underlying tree structures of reference concepts (RCs). (Remember there are about 58,000 RCs across all of KBpedia.) We call each tree structure a ‘typology’, which has a root concept that is one of the upper SuperType concepts. The tree structures in each typology are built from rdfs:subClassOf relations, also known as ‘is-a‘. The typologies range in size from a few hundred RCs to multiple thousands in some cases. The combination of the upper KKO structure and its supporting 70 or so typologies provide the conceptual backbone to KBpedia. We discussed this general terminology in our earlier CWPK #18 installment. Each typology extracted from KBpedia can be inspected as a standalone ontology in something like the Protégé IDE. Typologies can be created or modified offline and then imported back into KBpedia, steps we will address in later installments. The individual typologies are modular in nature, and a bit easier to inspect and maintain when dealt with independently of the entire KBpedia structure. Starting and Load We begin with our standard opening routine, though we are a bit more specific about identifying prefixes in our name spaces: Which environment? The specific load routine you should choose below depends on whether you are using the online MyBinder service (the ‘raw’ version) or local files. The example below is based on using local files (though replace with your own local directory specification). If loading from MyBinder, replace with the lines that are commented (#) out. main =…
topic: CWPK
topic: KBpedia
topic: Semantic Web Tools
links to: Cooking with Python and KBpedia
links to: Python
links to: KBpedia
links to: ontology
links to: KKO
links to: CWPK #18
links to: Protégé
links to: IDE
links to: cb1-1
links to: cb1-2
links to: cb1-3
links to: cb1-4
links to: cb1-5
links to: cb1-6
links to: cb1-7
links to: cb1-8
links to: cb1-9
links to: cb1-10
links to: cb1-11
links to: cb1-12
links to: cb1-13
links to: cb1-14
links to: cb1-15
links to: cb1-16
links to: cb1-17
links to: cb1-18
links to: cb2-1
links to: cb2-2
links to: cb2-3
links to: cb4-1
links to: cb4-2
links to: cb5-1
links to: cb7-1
links to: cb7-2
links to: cb7-3
links to: cb7-4
links to: cb7-5
links to: cb7-6
links to: cb8-1
links to: cb8-2
links to: cb8-3
links to: cb8-4
links to: cb8-5
links to: cb8-6
links to: cb8-7
links to: cb8-8
links to: cb8-9
links to: cb9-1
links to: cb10-1
links to: cb10-2
links to: cb10-3
links to: cb10-4
links to: cb10-5
links to: cb10-6
links to: cb10-7
links to: cb10-8
links to: cb10-9
links to: cb11-1
links to: cb12-1
links to: cb13-1
links to: cb13-2
links to: cb13-3
links to: cb13-4
links to: cb13-5
links to: cb13-6
links to: cb13-7
links to: cb13-8
links to: cb13-9
links to: cb13-10

Mike Bergman
type: User

Mike Bergman
type: Person

Cooking with Python and KBpedia
label: CWPK listing

Stack Overflow

2D lists

Arrays

KBpedia

direct download

notify me