Review Comment:
Overall evaluation
Select your choice from the options below and write its number below.
1
== 3 strong accept
== 2 accept
== 1 weak accept
== 0 borderline paper
== -1 weak reject
== -2 reject
== -3 strong reject
Reviewer's confidence
Select your choice from the options below and write its number below.
3
== 5 (expert)
== 4 (high)
== 3 (medium)
== 2 (low)
== 1 (none)
Interest to the Knowledge Engineering and Knowledge Management Community
Select your choice from the options below and write its number below.
4
== 5 excellent
== 4 good
== 3 fair
== 2 poor
== 1 very poor
Novelty
Select your choice from the options below and write its number below.
3
== 5 excellent
== 4 good
== 3 fair
== 2 poor
== 1 very poor
Technical quality
Select your choice from the options below and write its number below.
4
== 5 excellent
== 4 good
== 3 fair
== 2 poor
== 1 very poor
Evaluation
Select your choice from the options below and write its number below.
3
== 5 excellent
== 4 good
== 3 fair
== 2 poor
== 1 not present
Clarity and presentation
Select your choice from the options below and write its number below.
4
== 5 excellent
== 4 good
== 3 fair
== 2 poor
== 1 very poor
Review
This paper presents a workflow for adding semantics to Wikipedia links. Instead of using a general "wikiPageWikilinks", the proposed workflow converts the pagelinks between Wikipedia entities into semantic triples. This work has the potential to further enrich the structured content of DBpedia, and is presented in a logical manner. However, some revisions are necessary to improve the work.
1. An important issue lies in the example given by the authors in the introduction section. The authors state that the link between "Paris" and "French Open" is under a general category of "dbpo:wikiPageWikiLink". However, this is not the case in the current DBpedia Paris page (see http://dbpedia.org/page/Paris). In this page, the entity of "Paris" has been linked to "French Open" through the relation of "is dbpedia-owl:location of" (In fact, there are entities of "dbpedia:1979_French_Open", "dbpedia:1981_French_Open", "dbpedia:1993_French_Open", and so forth). I even couldn't find the property called "wikiPageWikiLink", but only "wikiPageExternalLink". This could be due to recent updates of DBpedia, and I believe it should not be used as a reason to deny the authors' good work, since this workflow can also be applied to other general pagelinks. However, I think it is very important to change the introduction text accordingly; otherwise, a reader may get confused by the motivation of the paper. A question that a confused reader may directly ask is: why are you still doing this work since the DBpedia links are already assigned semantics? Thus, it would be helpful if the paper can address this issue, and emphasize the general application of this research in the introduction.
2. The presented work heavily relies on the authors' previous work FRED. However, the link to FRED cannot be accessed. I tried to visit the site on two separate days, but didn't get any luck on either of the two days. It would be good if the authors can ensure a running page of FRED, so that interested readers can check it.
3. While the links to Waston and LOV are accessible, the link to NELL also can't be visited. I tried twice in two separate days as I did for the FRED link.
4. The url to the experiment result http://isotta.cs.unibo.it:9191/sparql is not accessible as well, which makes it difficult to see the experiment result.
5. In the evaluation section, the authors used precision, recall, F-measure, and Kendall's W to evaluate the accuracy of the generated relations. Likert scales have been used to ask three users to evaluate the quality of the generated relations. However, it is not clear how these indicators (e.g., precision or recall) are calculated. Are the authors calculating the precision based on the number of "strongly agree" divided by the total number of relations? How about recall, and what are the all relevant relations which should be used as the denominator for the calculation. Without a clear description on the calculation process, it would be difficult to understand the experiment results.
To sum up, while this paper has several not working links and some issues, there exist good values in the presented workflow, which deserves a publication.
|