Skip to main navigation Skip to search Skip to main content

Approximate SPARQL for error tolerant queries on the DBpedia knowledge base

  • CUBRC

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

The Resource Description Framework (RDF), a language for describing resources, is being used more commonly in information fusion systems. SPARQL is a standard query language that enables knowledge extraction from data encoded in RDF. A SPARQL query is, in essence, an exact subgraph matching problem. Unfortunately, many of the techniques that produce data in RDF (such as manual data entry, social network analysis, natural language processing, etc.) make annotation mistakes, which result in dirty RDF data. SPARQL performs suboptimally on RDF data containing errors since, as an exact graph matching tool, it is not designed to cope with noisy data. To improve knowledge extraction under these conditions, we propose an extension to SPARQL that permits approximate graph matches. This allows queries to cope with errors in the RDF graph, both on the attribute level (such as misspelled names) as well as on the structural level (missing or extra edges). We use the TruST heuristic algorithm to solve the underlying approximate graph matching problem and demonstrate the benefit it brings to answering questions on the DBpedia knowledge base.

Original languageEnglish
Title of host publicationProceedings of the 16th International Conference on Information Fusion, FUSION 2013
Pages850-856
Number of pages7
StatePublished - 2013
Event16th International Conference of Information Fusion, FUSION 2013 - Istanbul, Turkey
Duration: Jul 9 2013Jul 12 2013

Publication series

NameProceedings of the 16th International Conference on Information Fusion, FUSION 2013

Conference

Conference16th International Conference of Information Fusion, FUSION 2013
Country/TerritoryTurkey
CityIstanbul
Period07/9/1307/12/13

Fingerprint

Dive into the research topics of 'Approximate SPARQL for error tolerant queries on the DBpedia knowledge base'. Together they form a unique fingerprint.

Cite this