Figure 2 - uploaded by Valentina Anita Carriero
Content may be subject to copyright.
6: Infrequently changed properties from the added file 7: Infrequently changed properties from the removed file

6: Infrequently changed properties from the added file 7: Infrequently changed properties from the removed file

Source publication
Preprint
Full-text available
One of the grand challenges discussed during the Dagstuhl Seminar "Knowledge Graphs: New Directions for Knowledge Representation on the Semantic Web" and described in its report is that of a: "Public FAIR Knowledge Graph of Everything: We increasingly see the creation of knowledge graphs that capture information about the entirety of a class of ent...

Contexts in source publication

Context 1
... frequency of each property was calculated, irrespective of the subjects and objects connected through them for both the 'Added' and 'Removed' files. Each property was ranked based on its frequency in the 'Added' Fig. 2.3and the 'Removed' Fig. 2.4 files. This provided us with the top twenty most frequently added properties ( Fig. 2.2) and removed properties ( Fig. 2.1). This shows that at least fifteen properties are common between the frequently added and deleted properties Fig. 2.5. Fig 2.3 represents all the properties that were added to the DS2 ...
Context 2
... frequency of each property was calculated, irrespective of the subjects and objects connected through them for both the 'Added' and 'Removed' files. Each property was ranked based on its frequency in the 'Added' Fig. 2.3and the 'Removed' Fig. 2.4 files. This provided us with the top twenty most frequently added properties ( Fig. 2.2) and removed properties ( Fig. 2.1). This shows that at least fifteen properties are common between the frequently added and deleted properties Fig. 2.5. Fig 2.3 represents all the properties that were added to the DS2 version of DBpedia. The area ...
Context 3
... frequency of each property was calculated, irrespective of the subjects and objects connected through them for both the 'Added' and 'Removed' files. Each property was ranked based on its frequency in the 'Added' Fig. 2.3and the 'Removed' Fig. 2.4 files. This provided us with the top twenty most frequently added properties ( Fig. 2.2) and removed properties ( Fig. 2.1). This shows that at least fifteen properties are common between the frequently added and deleted properties Fig. 2.5. Fig 2.3 represents all the properties that were added to the DS2 version of DBpedia. The area of each property is based on its frequency in the 'Added' file. The more frequently a ...
Context 4
... each property was calculated, irrespective of the subjects and objects connected through them for both the 'Added' and 'Removed' files. Each property was ranked based on its frequency in the 'Added' Fig. 2.3and the 'Removed' Fig. 2.4 files. This provided us with the top twenty most frequently added properties ( Fig. 2.2) and removed properties ( Fig. 2.1). This shows that at least fifteen properties are common between the frequently added and deleted properties Fig. 2.5. Fig 2.3 represents all the properties that were added to the DS2 version of DBpedia. The area of each property is based on its frequency in the 'Added' file. The more frequently a property was added, the larger the ...
Context 5
... 'Removed' files. Each property was ranked based on its frequency in the 'Added' Fig. 2.3and the 'Removed' Fig. 2.4 files. This provided us with the top twenty most frequently added properties ( Fig. 2.2) and removed properties ( Fig. 2.1). This shows that at least fifteen properties are common between the frequently added and deleted properties Fig. 2.5. Fig 2.3 represents all the properties that were added to the DS2 version of DBpedia. The area of each property is based on its frequency in the 'Added' file. The more frequently a property was added, the larger the area. At the bottom right corner we see a large area with three dots in it, representing the expansion of the graph to ...
Context 6
... shows that at least fifteen properties are common between the frequently added and deleted properties Fig. 2.5. Fig 2.3 represents all the properties that were added to the DS2 version of DBpedia. The area of each property is based on its frequency in the 'Added' file. ...
Context 7
... the bottom right corner we see a large area with three dots in it, representing the expansion of the graph to see less frequently added properties. Fig 2.4 represents all the properties that were removed from DS1. It can be interpreted similarly to the previous figure representing the added properties. ...
Context 8
... Fig 2.2 and Fig 2.1, we see that birth date, alias, area code and birth year were frequently added in DS1, whereas these properties are not in the top twenty frequently removed properties. This is reasonable, as properties such as birth date and birth year do not change frequently, unless it requires a correction. ...
Context 9
... the relative change rate for each of the property was calculated by using Eq.2.1. From Figure 2.8, it is observed that the property -"foaf:page" has the highest ratio, which means in 2015 pages have been edited way more than those in 2014. "DBpedia:webcast" was ranked the second. ...
Context 10
... more specialized or more general. To achieve that, we queried the data from DS1-MP, DS1-IT, DS2-MP and DS2-IT to obtain the classes of the objects in the older and newer versions, for a fixed properties. Later, we counted the number of objects that register a type change on a given property in order to explore the dynamics present in the data. Fig. 2.10 shows a network representing the dynamics of the type of the entities in DBpedia. It contains the relationships of the classes that presented more than 100 changes from or to them. The size of the nodes is proportional to the total number of changes. The edges represent the properties that are affected by these type changes, their ...
Context 11
... as a type for the property dbo:recordLabel. Some other interesting changes happen with the properties dbo:birthplace and dbo:nationality, which use to have range dbo:PopulatedPlace and dbo:Country respectively, now they present a type migration that includes dbo:Settlement and dbo:EthnicGroup resp. thus representing reality in a more precise way. Fig. 2.11 shows the properties that produced the lesser amount of type changesless than 10. Visual marks refer to the same variables as Fig. 2.10. We can see an increase in the number of properties, meaning that most of them are static in terms of type evolution. Some of the properties in this group are dbo:musicalArtist, dbo:leader, ...
Context 12
... which use to have range dbo:PopulatedPlace and dbo:Country respectively, now they present a type migration that includes dbo:Settlement and dbo:EthnicGroup resp. thus representing reality in a more precise way. Fig. 2.11 shows the properties that produced the lesser amount of type changesless than 10. Visual marks refer to the same variables as Fig. 2.10. We can see an increase in the number of properties, meaning that most of them are static in terms of type evolution. Some of the properties in this group are dbo:musicalArtist, dbo:leader, dbo:location, dbo:occupation, dbo:owner, and dbo:succesor. We see that it is unlikely for these properties to present a radical change of their ...
Context 13
... 2.10. We can see an increase in the number of properties, meaning that most of them are static in terms of type evolution. Some of the properties in this group are dbo:musicalArtist, dbo:leader, dbo:location, dbo:occupation, dbo:owner, and dbo:succesor. We see that it is unlikely for these properties to present a radical change of their range. In Fig. 2.11 it can be appreciated that the classes that receive new entities are more general, as the likes of dbo:Person, dbo:Agent, dbo:Place, and ...
Context 14
... analysis can also be generalized to define a metric of the volatility of the involved properties. Figure 2.10: Type Evolution Graph. ...
Context 15
... frequency of each property was calculated, irrespective of the subjects and objects connected through them for both the 'Added' and 'Removed' files. Each property was ranked based on its frequency in the 'Added' Fig. 2.3and the 'Removed' Fig. 2.4 files. This provided us with the top twenty most frequently added properties ( Fig. 2.2) and removed properties ( Fig. 2.1). This shows that at least fifteen properties are common between the frequently added and deleted properties Fig. 2.5. Fig 2.3 represents all the properties that were added to the DS2 ...
Context 16
... frequency of each property was calculated, irrespective of the subjects and objects connected through them for both the 'Added' and 'Removed' files. Each property was ranked based on its frequency in the 'Added' Fig. 2.3and the 'Removed' Fig. 2.4 files. This provided us with the top twenty most frequently added properties ( Fig. 2.2) and removed properties ( Fig. 2.1). This shows that at least fifteen properties are common between the frequently added and deleted properties Fig. 2.5. Fig 2.3 represents all the properties that were added to the DS2 version of DBpedia. The area ...
Context 17
... frequency of each property was calculated, irrespective of the subjects and objects connected through them for both the 'Added' and 'Removed' files. Each property was ranked based on its frequency in the 'Added' Fig. 2.3and the 'Removed' Fig. 2.4 files. This provided us with the top twenty most frequently added properties ( Fig. 2.2) and removed properties ( Fig. 2.1). This shows that at least fifteen properties are common between the frequently added and deleted properties Fig. 2.5. Fig 2.3 represents all the properties that were added to the DS2 version of DBpedia. The area of each property is based on its frequency in the 'Added' file. The more frequently a ...
Context 18
... each property was calculated, irrespective of the subjects and objects connected through them for both the 'Added' and 'Removed' files. Each property was ranked based on its frequency in the 'Added' Fig. 2.3and the 'Removed' Fig. 2.4 files. This provided us with the top twenty most frequently added properties ( Fig. 2.2) and removed properties ( Fig. 2.1). This shows that at least fifteen properties are common between the frequently added and deleted properties Fig. 2.5. Fig 2.3 represents all the properties that were added to the DS2 version of DBpedia. The area of each property is based on its frequency in the 'Added' file. The more frequently a property was added, the larger the ...
Context 19
... 'Removed' files. Each property was ranked based on its frequency in the 'Added' Fig. 2.3and the 'Removed' Fig. 2.4 files. This provided us with the top twenty most frequently added properties ( Fig. 2.2) and removed properties ( Fig. 2.1). This shows that at least fifteen properties are common between the frequently added and deleted properties Fig. 2.5. Fig 2.3 represents all the properties that were added to the DS2 version of DBpedia. The area of each property is based on its frequency in the 'Added' file. The more frequently a property was added, the larger the area. At the bottom right corner we see a large area with three dots in it, representing the expansion of the graph to ...
Context 20
... shows that at least fifteen properties are common between the frequently added and deleted properties Fig. 2.5. Fig 2.3 represents all the properties that were added to the DS2 version of DBpedia. The area of each property is based on its frequency in the 'Added' file. ...
Context 21
... the bottom right corner we see a large area with three dots in it, representing the expansion of the graph to see less frequently added properties. Fig 2.4 represents all the properties that were removed from DS1. It can be interpreted similarly to the previous figure representing the added properties. ...
Context 22
... Fig 2.2 and Fig 2.1, we see that birth date, alias, area code and birth year were frequently added in DS1, whereas these properties are not in the top twenty frequently removed properties. This is reasonable, as properties such as birth date and birth year do not change frequently, unless it requires a correction. ...
Context 23
... the relative change rate for each of the property was calculated by using Eq.2.1. From Figure 2.8, it is observed that the property -"foaf:page" has the highest ratio, which means in 2015 pages have been edited way more than those in 2014. "DBpedia:webcast" was ranked the second. ...
Context 24
... more specialized or more general. To achieve that, we queried the data from DS1-MP, DS1-IT, DS2-MP and DS2-IT to obtain the classes of the objects in the older and newer versions, for a fixed properties. Later, we counted the number of objects that register a type change on a given property in order to explore the dynamics present in the data. Fig. 2.10 shows a network representing the dynamics of the type of the entities in DBpedia. It contains the relationships of the classes that presented more than 100 changes from or to them. The size of the nodes is proportional to the total number of changes. The edges represent the properties that are affected by these type changes, their ...
Context 25
... as a type for the property dbo:recordLabel. Some other interesting changes happen with the properties dbo:birthplace and dbo:nationality, which use to have range dbo:PopulatedPlace and dbo:Country respectively, now they present a type migration that includes dbo:Settlement and dbo:EthnicGroup resp. thus representing reality in a more precise way. Fig. 2.11 shows the properties that produced the lesser amount of type changesless than 10. Visual marks refer to the same variables as Fig. 2.10. We can see an increase in the number of properties, meaning that most of them are static in terms of type evolution. Some of the properties in this group are dbo:musicalArtist, dbo:leader, ...
Context 26
... which use to have range dbo:PopulatedPlace and dbo:Country respectively, now they present a type migration that includes dbo:Settlement and dbo:EthnicGroup resp. thus representing reality in a more precise way. Fig. 2.11 shows the properties that produced the lesser amount of type changesless than 10. Visual marks refer to the same variables as Fig. 2.10. We can see an increase in the number of properties, meaning that most of them are static in terms of type evolution. Some of the properties in this group are dbo:musicalArtist, dbo:leader, dbo:location, dbo:occupation, dbo:owner, and dbo:succesor. We see that it is unlikely for these properties to present a radical change of their ...
Context 27
... 2.10. We can see an increase in the number of properties, meaning that most of them are static in terms of type evolution. Some of the properties in this group are dbo:musicalArtist, dbo:leader, dbo:location, dbo:occupation, dbo:owner, and dbo:succesor. We see that it is unlikely for these properties to present a radical change of their range. In Fig. 2.11 it can be appreciated that the classes that receive new entities are more general, as the likes of dbo:Person, dbo:Agent, dbo:Place, and ...
Context 28
... analysis can also be generalized to define a metric of the volatility of the involved properties. Figure 2.10: Type Evolution Graph. ...