alexa Utilizing DBpedia via CBR Approach of Recommender System | OMICS International
ISSN: 2277-1891
International Journal of Advance Innovations, Thoughts & Ideas
Make the best use of Scientific Research and information from our 700+ peer reviewed, Open Access Journals that operates with the help of 50,000+ Editorial Board Members and esteemed reviewers and 1000+ Scientific associations in Medical, Clinical, Pharmaceutical, Engineering, Technology and Management Fields.
Meet Inspiring Speakers and Experts at our 3000+ Global Conferenceseries Events with over 600+ Conferences, 1200+ Symposiums and 1200+ Workshops on
Medical, Pharma, Engineering, Science, Technology and Business

Utilizing DBpedia via CBR Approach of Recommender System

Nidhi Kushwaha*,Rajesh Mahule, and Vyas OP

Indian Institute of Information Technology, Allahabad, India

*Corresponding Author:
Nidhi Kushwaha
Indian Institute of Information Technology
Allahabad, India
E-mail: [email protected]

Received date: August 03, 2013; Accepted date: August 27, 2013; Published date: September 02, 2013

Citation: Kushwaha N, Rajesh M, Vyas OP (2013) Utilizing DBpedia via CBR Approach of Recommender System. Int J Adv Innovat Thoughts Ideas 2:148. doi:10.4172/2277-1891.1000148

Copyright: © 2013 Kushwaha N, et al. This is an open-access article distributed under the terms of the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.

Visit for more related articles at International Journal of Advance Innovations, Thoughts & Ideas


Semantic web; Linked data; Recommendation system; Content based

Importance and Need of LOD

Nowadays, the Internet enters in the stage where the information is being pushed by the people, for the people without considering their format. A revolutionary change in this continuation has been explored by the Linked Open Data Cloud Project [1]. Web contain heap of information, to gain knowledge from it, there is a need of technologies for handling the silos of data and provide only useful nuggets. It instigates the need of Recommender System, which means to provide on-time informative knowledge. Before the semantics, Recommender Systems are totally dependent on the knowledge of unstructured, semi-structured web or HTML (more specifically). These unstructured formats contain information that need suitable preprocessing for gaining content this is known as “content analysis” in Recommender System. Linked open Cloud comes into web since the beginning of 2008 by Sir Tim Berner’s Lee [1,2]. It takes the web into new higher position where one can share their knowledge by publishing data in one format i.e. RDF (Resource Description Framework). One can use the knowledge by SPARQL [3] querying on the RDF [4], and more than that utilize it by means of different applications. RDF comes as the counterpart of the traditional approaches but in a new and more efficient way, of data format and availability. Linked Open Data cloud [2] conceives semantic web with exploitation of linkages between concepts in the form of Ontologies [5]. Ontology is not a new term but it will take long time to make sufficient progress for converting the whole web into the concepts and relationships form. Linked Open Cloud is the collection of different but dependent Ontologies. These Ontologies is associated by manual or automatic tools [6]. Worldwide approval of LOD can be seen by the emergence of its dependent applications. Many research works [7] are going on for predicting the links between different datasets inside the Linked Open Data Cloud for the efficient utilization of this openly available web data. The pivot of the LOD is form by a giant encyclopedia termed as DBpedia [8,9] (the RDF version of Wikipedia info box) from which the other domain specific datasets are connected in a complementary way. There is a need to manage this huge amount of knowledge that present in both unstructured and structured format. Confinement of different domains in LOD is consisting of information of diverse sources like music, movie, drugs, geographic, government, protein sports, news and much more different information [8]. The information is in the form of triples that means subject, predicate, and object. LOD are based on five principles [1], one of which is to provide URIs to each and every resource for give it a universal uniqueness. This uniqueness of the items are helpful for gaining the information related to them throughout cross domain datasets like DBpedia, Freebase and also specific domain datasets like LinkedMDB1 for movie, DBTune2 for music. In the next section authors are explained related work in the field of LOD recommendation.

Related Work

Fetching information from a Knowledge Base which is not complete is of no use. Although datasets that consist in the LOD cloud not lie on this category, but they have inconsistencies in terms of their relationship. For example: In DBpedia book domain some important properties like “publisher”, “genre” is missing from some books. To gain the knowledge form the datasets it should be complete in all sense but in the other side achieving this is a hard problem for Miner. Previous approaches FeGeLOD [10], ExpLOD [11] uses the data sets that are not complete and enhance it with the help of DBpedia and YAGO ontology [12] of LOD Cloud. This enhancement depends on the hardcoded SPARQL queries embedded in the code. LOD Endpoints also gives different results from each other’s due to inconsistency of data storage. So, to utilize this knowledge is a challenging issue in sense of incomplete linkage facilities and inconsistencies. Mitigation of this problem is also a challenging task. This task includes generating more and more links between different datasets inside the LOD cloud. Although the RDF uses semantics to represent the data, it still have visualization problem. Various tools [13,14] are proposed for this purpose specifically. They all are based on nodes & links visualization. Visualization makes easy for quick understanding of the whole RDF graph. After the understanding of RDF graph we can apply various techniques to mine it or to gain information from it. Authors [14-17] proposed similarity matching and ML techniques like SVM to measure the similarity between two items and ultimately the results in RS. Approach [17] are considering only two hop depth for calculating weightage of a particular property we are here considering more than two hop. We are here discussing the key points and our finding while moving forward with the different approach of weight calculation for predicates related to the items (book domain).

Proposed Work

Authors are proposing a framework for weightage calculation form the given linkage properties of LOD. The knowledge base has linkage power, through which we can calculate which property or link is more suitable or appropriate for given item or seed point. The importance of the properties is dealing with the various attributes discussed with the help of definitions of the different links. Triplet form consists of <subject, predicate, object>. These objects act as a data source for particular a subject. Linkage between one subject to another object provides the capability of moving automatically form one source to another semantically. Here we describe about the linkage property which play significant role for particular item. These properties are defined with consideration of particular domain where the seed point is items which can be Movie, Music, Drug, Book or any Product.


InComg: Graph ‘G’, is form using collection of unique Subject, predicate, Object i.e <SiPiOi>. Here we consider that Graph ‘G’ denotes the datasets related to the particular domain. Let us assume a Subject ‘S’ as a seed point then all the links that act as object ‘O’ for ‘S’ is comes under “InComg” links. To count whole “InComg” gives us an idea of bag of resources that are connected to the particular seed point or Item ‘S’.

OutGog: In ‘G’= <Si,Pi,Oi>, if we consider object ‘O’ as our interest then all the linkage that points to it, is “OutGog” links. To count whole “OutGog” gives us an idea of bag of subjects or Items that are connected with objects.

ItmLinPs: In ‘G’= <Si,Pi,Oi>, if we consider specific property ‘Pi’ as our interest with the specific Item or subject ‘Si’ then all connected links are “ItmLinPs”.

PLinItm: In ‘G’=<Si,Pi,Oi>,’PLinItm’ can be calculated using counting the particular Item ‘Si’ related to the object ‘Oi’ with the specific property ‘Pi’. It illustrate that how much a particular property is powerful to explain an Item or subject.

PLinAll: In ‘G’=<Si,Pi,Oi>, we can calculate all the subjects that are related to different Items with the specific property and named as PLinAll. It is similar to the above property here we not consider only one specific Item.

ItmLinSamAs: LOD dataset “DBpedia” contains one very important predicate known as OwlSameAs. It has information about all the other terms in the Graph that are related to the particular Item or subject ‘Si’.

ItmDcSkosLin: Another more important property is Dcterms: subject that explains the resource or ‘Oi’ in more general terms. Skos: broader property describes categories related to Items particular object. Count of Dcterms: subject and Skos: broader gives us deeper understanding of the particular Item’s object. We are explaining the above definitions with the help of SPARQL query in Book domain in the Table 1.

Different Links SPARQL Query
InComg SELECT distinct count(?in) {?s a dbpedia-owl:Book. ?o ?in ?s.}
OutGog SELECT distinct count(?out) {?s a dbpedia-owl:Book.?s ?out ?o.}
ItmLinPs SELECT distinct count(?Ps) {<>  ?Ps ?o.}
AutLinItm SELECT distinct count(?author) {?s a dbpedia-owl:Book; dbprop:author ?author.}
GenreLinItm SELECT distinct count(?type) {?s a dbpedia-owl:Book. ?s dbprop:genre ?type.}
PubLinItm SELECT distinct count(?publisher) {?s a dbpedia-owl:Book; dbprop:publisher ?publisher.}
PLinAll SELECT distinct count(?p) {?s a dbpedia-owl:Book;  ?p  ?o.}
ItmLinSameAs SELECT distinct count(?o) {?s a dbpedia-owl:Book ?s owl:sameAs ?o.}
ItmDcSkosLin SELECT distinct count(?dcterm) count(?o) {?s a dbpedia-owl:Book ; dcterms:subject ?dcterm. ?dcterm skos:broader ?o}

Table 1: Definition description.

For Calculation of weightage of property we believe on a formula which is explained below. This will calculate the importance on a particular property in the whole RDF graph (Book graph in this case). Here we consider all the links that have the specific property (considering in the whole domain specific graph) as a denominator and number of link that one specific item consist related to that property. Like for example a specific Harry Potter book has total 42 links related to author property and total number of author property links are 38159 in the whole Book domain graph. Then the weightage of particular property is 2.88 for a specific Harry Potter book. Overall weightage is calculated by multiplying it with the total property links that are connected with specific Harry Potter book (including all properties author, publisher and genre) divided by total number of books in the whole domain specific RDF graph. By this way we can calculate the importance of particular property among all the properties for a specific book.

Formulae Used:

1. Weight for particular Property “αp

αp= PLinItm/ PLinAll

PLinItm and PLinAll are explained in above.

2. Overall weight calculation

Overall_weight = αp*ItmLinPs/1+logT

Here, T is the total number of items or subject that we consider for particular domain. By applying above formulae we obtained following matrix, where rows are populated with Items or subject s and columns are populated with properties of the Items fetched from DBpedia. The matrix is filled by the weights. After the application of above formula we get values of Table 2 Next section gives brief description of the implementation details.

Book Name Genere Author Publisher Dcterms:subject Owl:sameAs
The_Murder_of_Roger_Ackroyd 0.5523 0.0913 0.0294 0.019 0.0156
The_Mystery_of_the_Blue_Train 0.3474 0.043 0.0185 0.0119 0.0098
Elephants_Can_Remember 0.2663 0.044 0.0283 0.00367 0.0075
Life,_the_Universe_and_Everything 0.9162 0.0454 0.039 0.0151 0.0104

Table 2: Weight of different properties.


Identifying relevant datasets from dbpedia

DBpedia is the RDF encyclopedia, from which we have to extract selected information for further computations. It consists of 103 million triples incorporation of different information related to Animals (1,91,536), Species (2,69,060), Mammals (17,902), Persons (7,52,613), Cities (17,27,060), Places (12,48,585), organizations (2,11,525), Historic Places (5735), Historic Buildings (3435) , Drug (4,854), Companies (52,562), Films (1,23,530), Songs (5441), Albums (1,77,056), Museums (3023), Books (1,07919), Written Works (1,20,712) triples with total size 3GB. Querying through the endpoint [18] via internet takes more time then the querying with local repository. Today various RDF triple stores (Sesame [19], Allegrograph [20], OpenLink Virtuoso [21], Fuseki [22], 4Store [23], StarDog [24]) are present that have the capability to store the RDF triples in efficient manner for quick consumption. For testing purpose we choose Sesame 2.7, that can work with windows system with 3GB RAM. We store approx 50,595 triples of Book domain. With the help of Sesame Java API we are able to perform query on the Sesame triple store. We found various inconsistencies in the DBpedia Book dataset. Like the DBpedia illustrator property has 2478 and 1859 links (in the whole book graph) with the and respectively. Here in Table 3 we have mentioned some important properties that have larger links then others.

Property Links
type 240478
subject 9965
SameAs 48440
author 26634 (property)
author 26457 (ontology)
publisher 25015 (property)
isbn 21132 (ontology)
isbn 2085 (property)
mediaType 20393 (property)
rdflabel 20875
illustrator 1859 (ontology)
illustrator 2478 (property)
previous Work 7647 (ontology)

Table 3: Property links description (only some).

Thanks to the property path facility of SPARQL Query Language [3] that provide traversal path extraction through one to more distance from the seed point. This facility comes with SPARQL 1.1, the SPARQL query evaluation. To minimize the burden on the Sesame triple store we fetched subject’s category classification hierarchy (SKOS ontology) from the Virtuoso SPARQL endpoint. Deep extraction (more than 2 hop) of the hierarchy gives more generalized results in case of the skos: broader property which are not used in the previous approaches. By experiment we come to know that three levels deeper gives much generalized results like for category “Fantasy Anthologies Series” it give “Fantasy Anthologies” at level 1(1L), “Fiction Anthologies” at level 2 (2L) and which is further related to the category “Literature By Genre” at level 3 (3L) as mentioned in the Figure 1.


Figure 1: Levels description.

Although more generalized term “Literature By Genre” at level-3 are less informative, but we have also taken this into consideration of calculating the weights of the properties. After calculating weights regarding each book, the similarity metrics can be calculated. Table 4 shows the relatedness of the book URI “ The_Murder_of_Roger_Ackroyd” with the other books inside the DBpedia using Pearson Correlation similarity metric. Result of the semantic measures are describes with the following Table 4. In the table it is easily determine that the books sharing same genre, authors, and publisher have great number of similarity rather than others. For example first recommendation of the book for “The Murder of Roger Ackroyd” have same author “Agatha Christie” and they both shared same genre “Crime Novel”. So, if a person like the Crime Novels then its related books would be their right choice in future. This type of recommendation is called Content Based Recommendation (CBR). Web 3.0 gives the opportunity to the researcher to directly choose the related terms (objects) of the items (subject) from the statements (NTriples) considering their linkage type (predicates) like genre, publisher, and illustrator. Items sharing same objects in the RDF graph will be similar to each other because have something common. For Example, we know the fact that most people are interested to read the sequel of books, written by the same author. In the next section we discussed shortcomings and future scope related to our approach.

Table 4: Shows the relatedness of the “” with others.

Discussions and Future Scope

LOD is act as an evaluation of the knowledge base that contains huge interlinked information to share. In our dataset we consider only DBpedia dataset, while in future we definitely work with more than two or three related RDF datasets. Domain analysis also raises the quality of application specific tools because it consist specific information from different sources. The Giant Cloud has millions of triples which can be mine to gain interesting things. Recommending the predicates by ARM (Association Rule Mining) [25] can be possible if we consider the name of Books as the Context and mine the predicates (Authors, Publisher, Writer). While on the other hand mining the Book names in the context of their objects (J.K. Rowling, Fantasy book, Harry_Potter Series) cluster the similar types of books on the basis of their frequently co-occurring. In future we mine with the different datasets in various contexts to gain recommendation from the triples. We will apply this knowledge to cluster the same type of books by matching their user specific properties. Like if a person give more interested to read a book of particular author or particular publication we can able to recommend him/her without worrying other properties of the book.


In this paper we have discussed about the advantage of Web 3.0 in the field of Recommender System. Although the paper based on the suitability of the Content Method with Web 3.0, Collaborative Filtering is not totally fit for that. It is because of the lack of the reviewing information in the LOD Cloud. Reason for this can be better understand in terms of privacy preservation of personal data. Content based approach also has some difficulties in it. One of them is to extract knowledge from LOD Cloud. It is not easy due to unclear boundary of the graph. Visualizing the graph as a whole is also not the solution for it. We have used Semantic web plug-in of the Gephi [13] tool to visualize the only one (publisher) property of the Harry potter book describe in Figure 2. Visualization of RDF graph gives us a realization of how different properties are related to different subjects and ease of SPARQL querying on them. In the above approach we manually select the interesting features of the item like publisher, genre etc. In future we will try to apply automatic approach of selection of properties to give our system more automation. Presently we are only using DBpedia dataset that are very noisy and huge. For the future point of view we will integrate more domain specific RDF datasets to give reality to our system.


Figure 2: Visualization of publisher property of the book “harry potter and the prisoner of Azkaban”.


    Bauer F, Kaltenböck M (2011) Linked Open Data:The Essentials. edition mono/monochrom, Vienna, Austria.
Select your language of interest to view the total content in your interested language
Post your comment

Share This Article

Relevant Topics

Article Usage

  • Total views: 11864
  • [From(publication date):
    November-2013 - Jun 20, 2018]
  • Breakdown by view type
  • HTML page views : 8051
  • PDF downloads : 3813

Post your comment

captcha   Reload  Can't read the image? click here to refresh

Peer Reviewed Journals
Make the best use of Scientific Research and information from our 700 + peer reviewed, Open Access Journals
International Conferences 2018-19
Meet Inspiring Speakers and Experts at our 3000+ Global Annual Meetings

Contact Us

Agri & Aquaculture Journals

Dr. Krish

[email protected]

+1-702-714-7001Extn: 9040

Biochemistry Journals

Datta A

[email protected]

1-702-714-7001Extn: 9037

Business & Management Journals


[email protected]

1-702-714-7001Extn: 9042

Chemistry Journals

Gabriel Shaw

[email protected]

1-702-714-7001Extn: 9040

Clinical Journals

Datta A

[email protected]

1-702-714-7001Extn: 9037

Engineering Journals

James Franklin

[email protected]

1-702-714-7001Extn: 9042

Food & Nutrition Journals

Katie Wilson

[email protected]

1-702-714-7001Extn: 9042

General Science

Andrea Jason

[email protected]

1-702-714-7001Extn: 9043

Genetics & Molecular Biology Journals

Anna Melissa

[email protected]

1-702-714-7001Extn: 9006

Immunology & Microbiology Journals

David Gorantl

[email protected]

1-702-714-7001Extn: 9014

Materials Science Journals

Rachle Green

[email protected]

1-702-714-7001Extn: 9039

Nursing & Health Care Journals

Stephanie Skinner

[email protected]

1-702-714-7001Extn: 9039

Medical Journals

Nimmi Anna

[email protected]

1-702-714-7001Extn: 9038

Neuroscience & Psychology Journals

Nathan T

[email protected]

1-702-714-7001Extn: 9041

Pharmaceutical Sciences Journals

Ann Jose

[email protected]

1-702-714-7001Extn: 9007

Social & Political Science Journals

Steve Harry

[email protected]

1-702-714-7001Extn: 9042

© 2008- 2018 OMICS International - Open Access Publisher. Best viewed in Mozilla Firefox | Google Chrome | Above IE 7.0 version
Leave Your Message 24x7