SEMLIB Final Conference | DERI presentation


Published on

SLRD, the SEMLIB Linked Data Recommendation Engine

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

SEMLIB Final Conference | DERI presentation

  1. 1. The SemLib Linked Data RecommendationEngine
  2. 2. Our participation — and motivation — in the project involved the research & development of a recommendation engine that...● leveraged the ubiquitousness and richness of linked data from the Web of Data● would produce new linked data as a result of those recommendations. In addition, this would provide data interlinking
  3. 3. In general, we were concerned with...●How to perform recommendation computationswith the linked data? Furthermore, how to do thisscalably?● How to input linked data into such a system?●How to output linked data from thoserecommendations?
  4. 4. For recommendation types, we focused onimplementing the primary types: Collaborative filtering & Content-based With an array of algorithms including — Cosine Similarity, Pearson Correlation, Jaccard Distance, Co-occurrence, etc.●An initial direction for the computation ofrecommendations ✓Challenge: adapting these algorithms for linked●data ✓
  5. 5. SPARQL for the Input of Linked Data SELECT ?s ?nationality ?influences WHERE { ?s dbpedia-ontology:occupation dbpedia- resource:Poet. ?s dbpedia-property:influences ?influences. ?s dbpedia-ontology:nationality ?nationality. }●Declarative and expressive method for data materialisation ✓●SPARQL endpoint communication ✓
  6. 6. Output computed recommendations as linked RDF data. ⟨⟩ semlibproject:hasRecommendation _:node175. _:node175 ⟨semlibproject:recommends⟩ ⟨⟩. _:node175 ⟨semlibproject:hasScore⟩ 240.0. RDF creation and interlinking ✓ ●
  7. 7. Sometimes...Linked data → Big data Therefore, we went in the direction of a distributed and parallel framework — MapReduce
  8. 8. Overview of Results● SPARQL execution, RDF materialisation and output → design the system using established tools and libraries● The adaptation of the recommendation algorithms for RDF → formalisations presented in a paper [ECAI 2012]● Scalability with the possibly large amount of data that can be input → a parallel and distributed framework
  9. 9. ImplementationOur FrameworkSPARQL Query Extraction/CommunicationMachine Learning/Recommendation AlgorithmsAs well as other technologies and libraries
  10. 10. Deployment and UseTo get SLDR running, a JSP web server, such as Tomcat or Jetty is required.SLDR is deployed as a web application (WAR). From there, the recommendation engine is fully accessible from your web browser to start creating and running jobs.
  11. 11. The Recommendation Job Control Panel Saved Jobs Active Status Output
  12. 12. A Recommendation Job Algorithm SelectionSPARQL Endpoints Query Configuration
  13. 13. The Backend System Workflow
  14. 14. Retrieving RecommendationsUsers have the option of viewing computed recommendations through either SPARQL and the output triplestore or through a REST API implemented into the systems backend.The REST API can be utilised for better integration into already existing systems (e.g. HTML, JavaScript, etc.)
  15. 15. Summary● Ongoing improvement and development● Have tested sucessfully with some of the SMEs● More information available at