<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>What SPARQL Query Logs Tell and do not Tell about Semantic Relatedness in LOD</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jochen Huelss</string-name>
          <email>jochen@huelss.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Heiko Paulheim</string-name>
          <email>heiko@dwslab.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of Mannheim Research Group Data and Web Science</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>Linked Open Data browsers nowadays usually list facts about entities, but they typically do not respect the relatedness of those facts. At the same time, query logs from LOD datasets hold information about which facts are typically queried in conjunction, and should thus provide a notion of intra-fact relatedness. In this paper, we examine the hypothesis how query logs can be used to improve the display of information from DBpedia, by grouping presumably related facts together. The basic assumption is that properties which frequently co-occur in SPARQL queries are highly semantically related, so that co-occurence in query logs can be used for visual grouping of statements in a Linked Data browser. A user study, however, shows that the grouped display is not signi cantly better than simple baselines, such as the alphabetical ordering used by the standard DBpedia Linked Data interface. A deeper analysis shows that the basic assumption can be proven wrong, i.e., co-occurrence in query logs is actually not a good proxy for semantic relatedness of statements.</p>
      </abstract>
      <kwd-group>
        <kwd>Semantic Relatedness</kwd>
        <kwd>Linked Open Data</kwd>
        <kwd>Linked Data Browsers</kwd>
        <kwd>Query Log Mining</kwd>
        <kwd>DBpedia</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Usefulness is considered as one of the key challenges to human users who
attempt to bene t from the immense knowledge graph of semantic web [13]. This
challenge implies that the user experience and visual presentation of linked data
is currently not tangible for human users. Back in 2006, this lack of a tool which
enables a curated, grouped, and sorted browsing experience of semantic data
describing real-world entities was also mentioned by Sir Tim Bernes Lee in a talk on
the Future of the Web at University of Oxford1. With the web of Linked Data
having grown to more than 1,000 datasets [15], and the emergence of central
1 http://webcast.oii.ox.ac.uk/?view=Webcast&amp;ID=20060314
hubs in the semantic web such as DBpedia, the semantic web research
community has put a lot of e ort into the elds of browsing and interacting with linked
data [
        <xref ref-type="bibr" rid="ref4">4, 8</xref>
        ] and summarizing important properties of a semantic entity. However,
these problems persist since all major semantic web databases and browsers still
present their linked data as an unordered or lexicographically ordered list to
their users.
      </p>
      <p>Traditionally, web usage logs are mined for behavioral patterns to cluster
items of common interest and recommend them to users. Our approach applies
web usage mining on SPARQL query logs and looks for patterns that relate
equally interesting properties of semantic entities. Thus, our general hypothesis
is that, in a data set of SPARQL queries, it should be possible to mine
information about the semantic relatedness of statements. Such information again can
be exploited to form coherent groups of properties which are bene cial for the
human browsing experience of the semantic web.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>
        Although much work has been devoted to the creation of browsers for Linked
Open Data, most of them essentially present facts about entities as lists, in
which the facts have no relation among each other [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Examples for such
classic browsers are DISCO 2 and Tabulator [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. A semantic grouping of facts, as
proposed in this paper, has been rarely proposed so far.
      </p>
      <p>Some browsers, such as Zitgist 3, provide domain-speci c templates that order
information which uses popular ontologies, such as FOAF4 or the Music
Ontology5. While there is a trend towards reusing popular vocabularies for LOD, there
is, at the same time, a trend towards using multiple vocabularies in parallel [15],
which, in turn, creates new challenges for such template-based approaches.</p>
      <p>
        A slightly di erent, yet related problem is the ranking and ltering of
semantic web statements into more and less relevant ones. Here, some works have
been proposed in the past, e.g., [
        <xref ref-type="bibr" rid="ref3 ref5 ref6">3, 5, 6, 9, 17</xref>
        ].
      </p>
      <p>In [16], we have presented a rst domain-independent attempt of creating a
semantic grouping of facts. Here, we try mapping predicates to WordNet synsets,
and measure the similarity among predicates in WordNet. Similar predicates are
grouped together, with the labels for synsets of common ancestors being used as
group headings. Like the work presented in this paper, no statistical signi cant
improvements over baseline orderings of facts could be reported.
2 http://wifo5-03.informatik.uni-mannheim.de/bizer/ng4j/disco/
3 Meanwhile o ine
4 http://www.foaf-project.org/
5 http://musicontology.com/
In this paper, we present an approach for semantically grouping semantic web
statements, based on SPARQL query logs. Those logs are read once and
preprocessed into a database schema including basic statistics, as shown in Fig. 1.</p>
      <p>
        Given that a user requests a URI, such as http://dbpedia.org/resource/
Mannheim, the system rst reads the corresponding set of triples, then uses the
preprocessed database to create a grouping, with di erent possible algorithms
(see below). The result of grouped statements is delivered to the user through
the modular semantic web browser MoB4LOD 6.
The basis of our experiments is the UseWOD 2014 SPARQL dataset [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], which
collects 300k SPARQL queries for the public DBpedia endpoint7 over the
period 06/12/2013 { 01/27/2014, out of which 249k are valid SPARQL queries,
6 http://www.ke.tu-darmstadt.de/resources/mob4lod
7 http://dbpedia.org/sparql
the vast majority (more than 98%) being SELECT queries.8 The dataset is fully
anonymized.
      </p>
      <p>From those SPARQL queries, we extract triple patterns for further analysis.
Fig. 2 depicts the distribution of the number of triple patterns over the dataset,
showing that most of the datasets have only one triple pattern, while there is an
anomaly at nine triple patterns, caused by a bot posing almost the same query
repeatedly.</p>
      <p>In particular, for our goal of semantically grouping statements, we are
interested in property pairs and class-property pairs, i.e., pairs of two properties, or a
property and a class, co-occurring in a query. From the 171k queries with more
than one triple in the query pattern, we extracted a total of 12,078 unique
property pairs and 1,141 unique class-property pairs. Here, we could use all triple
patterns that do not have a variable in the predicate position, which holds for
more than 80% of the triple patterns. During the pre-processing phase, we
collect the frequency of each of those pairs, as well as of all class-property pairs, as
shown in Fig. 1.
3.2</p>
      <sec id="sec-2-1">
        <title>Approaches for Grouping Statements</title>
        <p>For displaying results, we use two baseline approaches, as well as three
approaches based on clustering statements together that have predicates often
requested together.</p>
        <p>Baseline 1: Lexicographic The rst baseline follows the approach of
traditional semantic web browsers, ordering facts about an entity lexicographically
8 Note that the approach is not limited to DBpedia, but could be applied to any
dataset for which such a log le exists.
by their predicate. Groups are created by starting letters of the properties (A-F,
G-K etc.).</p>
        <p>Baseline 2: Counting The second baseline simply orders properties by their
frequency in the SPARQL log for the class the retrieved resource belongs to. No
grouping is made.</p>
        <p>Approaches based on clustering To create groupings of statements for
properties that co-occur frequently, we use three di erent clustering algorithms:
DBSCAN [7], hierarchical clustering [18], and Partitioning Around Medoids (PAM),
an implementation of k-medoids [10]. For the latter, we chose to use k = 7, so that
seven groups of statements are produced, following the wide-spread paradigm
that humans can perceive roughly seven items at once [12].</p>
        <p>For all clustering algorithms, we use the implementation in WEKA [19] with
the following distance function between two properties:
distance(p1; p2) =</p>
        <p>1
countp1;p2 + !
(1)
With this formula, the distance between two properties is the larger the more
often they are queried together. ! is used as a smoothing factor which prevents
a division by zero for pairs of properties that never occur together, and that
in uences the steepness of the curve between 0 and 1 co-occurences.</p>
        <p>In our experiments, we have used ! = 5. Furthermore, the following settings
were used: (1) the top-7 properties showing the highest support count in the
UseWOD queries were excluded from clustering since they are merely general
purpose properties, such as rdf:type and owl:sameAs, and (2) properties not
occurring at all in UseWOD data set were also excluded. The clusters shaped
were ranked descendingly based on the median value for support of the properties
assigned to a cluster. The employment of a median was anticipated to be better
than an average function because it is not prone to very high or low outliers
within the clusters.
4</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Evaluation</title>
      <p>We have evaluated the three di erent grouping options of our approach against
the two baselines in an end-user study. In that study, users were presented an
entity from DBpedia with the statements grouped according to one of the ve
approaches, and had to answer a question about the entity.
4.1</p>
      <sec id="sec-3-1">
        <title>Setup</title>
        <p>
          The study was conducted as an online experiment using the MoB4LOD semantic
web browser introduced above. A sample screenshot for the property grouping
for the DBpedia entity Cambridge is shown in Fig. 3. The hypotheses of this
study are derived from studies conducted by [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ], [14], and [16]:
H1 A participant nds a required fact signi cantly faster with a grouping based
on our approach than with a baseline.
        </p>
        <p>H2 The participant's subjective assessment of a grouping based on our approach
is signi cantly better than the sorting of baseline.</p>
        <p>H3 A participant is signi cantly more accurate in nding a required fact with
a grouping based on our approach than with a baseline.</p>
        <p>All of these hypotheses share the underlying assumption that the more
coherent, i.e. semantically-related groups of statements are, the easier it becomes for
humans to consume semantic web data and satisfy their information needs.</p>
        <p>For investigating these hypotheses, the online experiment employed a 5x5
within-subject design with ve questions and ve groupings (i.e. ve tasks) for
each participant. For each data sample, we measured the completion time of
a task (in seconds), the subjective assessment of a task (5-point Likert-type
scale), and the accuracy of an answer of a task (true / false). These data items
are the dependent variables for the study's independent variables which are the
ve sortings. The two baselines and the three groupings of our approach were
exposed to a participant in a randomized manner that ensured that each tasks
was answered equally often using one of the ve sortings. Table 1 depicts the
average number of groups and group sizes for each approach.
4.2</p>
      </sec>
      <sec id="sec-3-2">
        <title>Tasks and Users</title>
        <p>Each task of the online experiment consisted of a question and a grouped list of
semantically related properties of a speci ed DBpedia entity. The ve di erent
sortings were the actual stimulus material for evaluating our approach. For the
questions, entities from ve DBpedia classes were employed (Settlement, Film,
O ce Holder, Country, Musical Artist ). The chosen questions were intended
to not be answerable based on the participants' general knowledge. A sample
question of a task is: What is the elevation of the city of Mannheim? After each
question, the participants were asked for their subjective assessment of a listing.9
80 participants from Germany completed the experiment. They were
recruited by convenience sampling via social network sites, e-mailing, and other
online channels. To remove obvious outliers, we removed all experiment data
from participants who did not answer all questions, as well as those with a
completion time outside of a 3 con dence interval, i.e., extremely low or high
9 The questionnaire is available at http://dws.informatik.uni-mannheim.de/en/
research/noise-2015-accompanying-material
processing times. After data cleansing, the sample consisted of 65 participants,
which means that each question was solved 13 times with each sorting, on
average. Exactly 40% of the participants reported to be familiar with the concepts
of semantic web.
4.3</p>
      </sec>
      <sec id="sec-3-3">
        <title>Results</title>
        <p>For all hypotheses, the independent variable was the set of the ve sortings and
the hypotheses are individually analyzed on task level. An overall determination
of the best sorting is impossible because the equality of all tasks' level of di culty
cannot be assumed. Table 2 exposes the descriptive statistics (i.e. means of the
dependent variables) of our experiment to the readers.</p>
        <p>For the recorded completion times T1-5, the analysis of the means does not
lead to a conclusive picture. For three out of ve tasks, the best mean completion
is even taken by one of the baselines. A one-way ANOVA investigates pair-wise
signi cant di erences between the three groupings and the two baselines in case
of H1 and H2. For H1, only Task 1 depicted signi cant pair-wise di erences. A</p>
        <p>Dep. Variable Lexic. Baseline Count. Baseline DBSCAN Hier. Clustering PAM
Time T1
Time T2
Time T3
Time T4</p>
        <p>Time T5
Assessment
Accuracy
Bonferroni posthoc test indicated that the hierarchical clustering grouping had
a signi cant di erence with the simple count baseline (p &lt; :05). Therefore, H1
cannot be con rmed consistently across the tasks.</p>
        <p>Regarding the subjective assessment of the groupings, Table 2 shows the
average assessment for each grouping. The best assessment is given to the PAM
grouping which is contradictive to the completion time ndings. The executed
one-way ANOVA does not reveal any signi cant pair-wise di erences between
any of the cluster groupings and either one of the baselines. Therefore, also H2
cannot be con rmed for all tasks.</p>
        <p>The results of the experiment also show that the percentage of correctly
answered tasks exceeds 92% for all sortings (see Table 2). H3 cannot be validated
with an ANOVA since it is measured as a nominal variable. It can be accepted
or refused by using frequency scales partitioned by the di erent sortings.
However, these frequency scales revealed only non-signi cant di erences between the
groupings and the baselines. Thus, H3 cannot be con rmed either.</p>
        <p>To support the assumption of the previous section that an overall evaluation
of the hypotheses is impossible, Table 3 shows the mean working time and mean
assessment of all tasks. Time has got a range of 15.52 seconds. This indicates
that the di erent levels of di culty led to varying answering times. Moreover,
the table shows that the mean time and the mean assessment of the
individual questions correlate negatively using Pearson's correlation ( = 0:88). The
longer the time, the more negative the assessment. This nding is signi cant for
Tasks 3-5. Table 3 also shows that, for the chosen ontology classes, the number
of property pairs found in our database is small compared to the total amount
of triples retrieved for the DBpedia entities.
5</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Discussion</title>
      <p>The experiments presented in the previous section have shown that the
hypotheses formulated for this research work could not be con rmed, at least not for
DBpedia. In particular, the assumption that the visual grouping of properties
co-occurring in SPARQL logs leads to an improved human consumption of
semantic web data is proven wrong. Since three di erent clustering algorithms
were tried in the experiments, the cause is most likely not a shortcoming of the
clustering method, but the approach itself.</p>
      <p>The main weak point about the assumption is that SPARQL queries and
LOD interfaces serve the same information needs. First of all, a large fraction
of SPARQL queries are posed by machine agents, while Linked Data interfaces
are used by humans. Second, seasoned semantic web experts will be able to
use SPARQL as well as Linked Data interfaces, and choose among them given
the speci c characteristics of their problem. These di erences make the overall
assumption problematic.</p>
      <p>In the following, we will analyze this result in more detail. We exemplify
potential problems both with the approach as well as the evaluation methodology.
5.1</p>
      <sec id="sec-4-1">
        <title>Problems of the Approach</title>
        <p>An a posteriori analysis revealed that one central problem of the approach
presented in this paper is the coverage of the log le used for the experiments.
According to DBpedia mapping statistics10, there are currently 6,126 di erent
DBpedia ontology properties. In the UseWOD data set we found 488 pairs
consisting of DBpedia's ontology properties. Thus, the recall of class-property pairs
is 7.96% (given all of those pairs that appear for at least one entity in DBpedia).
For the property pairs generated from UseWOD, the recall is even lower at 1.9%
(again given all such pairs that appear for at least one entity in DBpedia). This,
in turn, means that the distance function for the majority of pairs is mostly
uniform (i.e., !1 ), with meaningful distances only assigned to a minority of pairs.</p>
        <p>Another problem we observed was that redundant properties (such as dbo:
birthPlace, dbp:birthPlace, and dbp:placeOfBirth) were rarely grouped
10 http://mappings.dbpedia.org/server/statistics/en/?show=100000
into the same cluster by any of the clustering based approaches. At second
glance, this is actually a built-in problem of the approach: when a user poses
a query against DBpedia, he or she will likely pick one of the properties, and
not use them in conjunction { for example, there are 2,687 using at least one of
the three aforementioned properties, but only 41 (i.e., 1.53%) use at least two of
those. This shows that redundant properties { which have the highest semantic
relatedness! { are unlikely to frequently co-occur in queries, and hence, are likely
not to end up in the same cluster.</p>
        <p>In informal feedback, many users complained that the groupings of
statements we created had only generic titles, which are essentially the cluster names
(group 1, group 2, etc.). Furthermore, DBSCAN identi es \noise points" which
do not belong to any cluster, that were displayed under the headline noise,
which lead to additional confusion. This shows that the assignment of
meaningful headlines to groups of statements is a desirable { if not required { property
of an approach like the one presented in this paper. This claim can be
formulated even more strongly, stating that grouping without assigning headlines is
pointless, since a user will have to scan each group for the desired piece of
information, and will thus not perceive any usability advantage. Assigning headlines
to groups, however, is a hard research problem in itself and was out of scope of
the research work.
5.2</p>
      </sec>
      <sec id="sec-4-2">
        <title>Problems of the Methodology</title>
        <p>Using lexicographic sorting as a baseline is a straightforward idea. Especially
since many tools use that ordering, it is also necessary to show that a signi cant
advancement can be made over that ordering in order to prove the utility of the
approach.</p>
        <p>However, in our case, the baseline is rather strong due to some
particular characteristics of DBpedia. DBpedia has two major namespaces { i.e.,
http://dbpedia .org/ontology/ holds all the higher quality properties mapped
against the DBpedia ontology, while http://dbpedia.org/property/ contains
the lower-quality, raw extraction from the Wikipedia infoboxes [11]. The
information conveyed by the former usually contains all the major information about
an entity. In lexicographic ordering by property URI, the properties from the
DBpedia ontology namespace are all listed before those from the raw extraction
namespace, which leads to the major facts presented way up in the list.</p>
        <p>Moreover, the properties that were required to answer the questions might
have a di erent perceived importance (comparing, e.g., the elevation of a city to
the governor of a state). Thus, users may implicitly search for properties they
deem more important further up on the list. Since this importance is also partly
re ected by the overall number of occurrences in DBpedia, this strategy may be
successful on the counting baseline, which may explain why this is also a very
strong baseline.</p>
        <p>When analyzing the results in more detail, we found that there is a
significant negative correlation between task completion time and assessment of the
presentation. At the same time, the presented entities had signi cantly di erent
sizes of the statement sets, which may furthermore in uence both the
completion time and the assessment. A more balanced selection of entities w.r.t. the
number of statement displayed may have lead to more conclusive results.
6</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Conclusion</title>
      <p>In this paper, we have analyzed how SPARQL query logs can be used for creating
meaningful groupings of statements for semantic web browsers. The analysis
of the results show that this is not possible for various reasons, including the
coverage of the SPARQL log les and blind spots of the approach, such as
redundant properties.</p>
      <p>In particular, it has been shown that co-occurence of properties in SPARQL
queries is not a suitable proxy to determine semantic relatedness of those
properties. This is best illustrated with the case of redundant properties, which are
maximally semantically related, but extremely unlikely to co-occur in a query.</p>
      <p>Many of the problems leading to the insigni cant results { e.g., the problem
of redundant properties or the strength of certain baselines { are speci c to one
dataset, in our case: DBpedia. For other datasets with di erent characteristics,
those problem may or may not hold. Thus, evaluations on other datasets than
DBpedia before eventually discarding the approach.</p>
      <p>Still, we think that nding ways to create semantically coherent, visually
appealing ways to present semantic web statements is a desirable property of
Linked Open Data browsers. We hope that the results presented in this paper
inspire future researchers to explore di erent ways of achieving that goal.
7. Ester, M., Kriegel, H.P., Sander, J., Xu, X.: A density-based algorithm for
discovering clusters in large spatial databases with noise. In: Proceedings of the 2nd
International Conference on Knowledge Discovery and Data Mining. pp. 226{231.</p>
      <p>Portland, USA (1996)
8. Garc a, R., Paulheim, H., Di Maio, P.: Special issue on semantic web interfaces.</p>
      <p>Semantic Web 6(8) (2015)
9. Kirchberg, M., Ko, R., Lee, B.S.: From linked data to relevant data - time is the
essence. In: Proceedings of the 1st International Workshop on Usage Analysis and
the Web of Data (USEWOD2011) at the 20th WWW Conference. Hyderabad,
India (2011)
10. Van der Laan, M., Pollard, K., Bryan, J.: A new partitioning around medoids
algorithm. Journal of Statistical Computation and Simulation 73(8), 575{584 (2003)
11. Lehmann, J., Isele, R., Jakob, M., Jentzsch, A., Kontokostas, D., Mendes, P.N.,
Hellmann, S., Morsey, M., van Kleef, P., Auer, S., et al.: Dbpedia-a large-scale,
multilingual knowledge base extracted from wikipedia. Semantic Web Journal (2014)
12. Miller, G.A.: The magical number seven, plus or minus two: some limits on our
capacity for processing information. Psychological Review 63(2), 81 (1956)
13. Moller, K., Hausenblas, M., Cyganiak, R., Handschuh, S.: Learning from linked
open data usage: Patterns &amp; metrics. In: Proceedings of the 2nd Web Science
Conference (WebSci10). Raleigh, USA (2010)
14. Paulheim, H.: Improving the usability of integrated applications by using
interactive visualizations of linked data. In: Proceedings of the ACM International
Conference on Web Intelligence, Mining and Semantics. Sogndal, Norway (2011)
15. Schmachtenberg, M., Bizer, C., Paulheim, H.: Adoption of the linked data best
practices in di erent topical domains. In: The Semantic Web{ISWC 2014, pp.
245{260. Springer (2014)
16. Seeliger, A., Paulheim, H.: A semantic browser for linked open data. In:
Proceedings of the Semantic Web Challenge at the 11th ISWC Conference. Boston, USA
(2012)
17. Thalhammer, A., Toma, I., Roa-Valverde, A., Fensel, D.: Leveraging usage data for
linked data movie entity summarization. In: Proceedings of the 2nd International
Workshop on Usage Analysis and the Web of Data (USEWOD2012) at the 21st
WWW Conference. Lyon, France (2012)
18. Ward Jr, J.H.: Hierarchical grouping to optimize an objective function. Journal of
the American Statistical Association 58(301), 236{244 (1963)
19. Witten, I., Frank, E., Hall, M.: Data Mining: Practical Machine Learning Tools and
Techniques: Practical Machine Learning Tools and Techniques. Morgan Kaufmann,
3rd edn. (2011)</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Berendt</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hollink</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hollink</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Luczak-Rosch</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , Moller,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Vallet</surname>
          </string-name>
          ,
          <string-name>
            <surname>D.</surname>
          </string-name>
          :
          <article-title>Usage analysis and the web of data</article-title>
          .
          <source>In: ACM SIGIR Forum</source>
          . vol.
          <volume>45</volume>
          , pp.
          <volume>63</volume>
          {
          <fpage>69</fpage>
          .
          <string-name>
            <surname>ACM</surname>
          </string-name>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Berners-Lee</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chen</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chilton</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Connolly</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dhanaraj</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hollenbach</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lerer</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sheets</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Tabulator: Exploring and analyzing linked data on the semantic web</article-title>
          .
          <source>In: Proceedings of the 3rd International Semantic Web User Interaction Workshop (SWUI2006) at the 5th ISWC Conference</source>
          . Athens, USA (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. Cheng, G.,
          <string-name>
            <surname>Tran</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Qu</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Relin: relatedness and informativeness-based centrality for entity summarization</article-title>
          .
          <source>In: Proceedings of the 10th International Semantic Web Conference (ISWC2011)</source>
          . pp.
          <volume>114</volume>
          {
          <fpage>129</fpage>
          . Bonn,
          <string-name>
            <surname>Germany</surname>
          </string-name>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Dadzie</surname>
            ,
            <given-names>A.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rowe</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Approaches to visualising linked data: A survey</article-title>
          .
          <source>Semantic Web</source>
          <volume>2</volume>
          (
          <issue>2</issue>
          ),
          <volume>89</volume>
          {
          <fpage>124</fpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Delbru</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Toupikov</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Catasta</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tummarello</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Decker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Hierarchical link analysis for ranking web data</article-title>
          .
          <source>In: The Semantic Web: Research and Applications</source>
          , pp.
          <volume>225</volume>
          {
          <fpage>239</fpage>
          . Springer (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Ding</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pan</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Finin</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Joshi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peng</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kolari</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Finding and ranking knowledge on the semantic web</article-title>
          .
          <source>In: Proceedings of the 4th International Semantic Web Conference (ISWC2005)</source>
          . pp.
          <volume>156</volume>
          {
          <fpage>170</fpage>
          .
          <string-name>
            <surname>Galway</surname>
          </string-name>
          ,
          <string-name>
            <surname>Ireland</surname>
          </string-name>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>