{'fraction_non_alphanumeric': 0.0199501246882793, 'fraction_numerical': 0.0, 'mean_word_length': 4.576388888888889, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Bridging the gap for retrieving DBpedia data

DBpedia is nowadays considered one of the main projects in the World Wide Web that extracts and enriches Wikipedia data in a structured form. Also, it is considered the central hub for the Linked Open Data. Querying DBpedia using big data approaches such as Hive-QL is regarded as one of the new techniques to solve the shortcomings of SPARQL; the main query language of DBpedia and the Semantic Web. Nevertheless, despite the speed of Hive-QL compared to SPARQL, it has a stability problem. Our paper presents a new architecture and implementation for querying DBpedia using Shark query language in addition to Hive-QL. As a result of this work, An obvious decrease in execution time, as well as, an increase in the degree of stability have been attained.