C3Subtitles: wikidatacon2019: Barriers to Using Wikidata as a Knowledge Base
back

Barriers to Using Wikidata as a Knowledge Base

If you suspend your transcription on amara.org, please add a timestamp below to indicate how far you progressed! This will help others to resume your work!

Please do not press “publish” on amara.org to save your progress, use “save draft” instead. Only press “publish” when you're done with quality control.

Video duration
00:25:57
Language
English
Abstract
-

At first glance Wikidata appears to be an excellent source of general background knowledge. It is large, contains generally high-quality information, contains a large ontology, and can be freely used. However, it ends up being difficult to use Wikidata as is, or even with minor modifications, as a knowledge base of general-purpose information.
First there are factual errors in Wikidata, such as the incorrect identification of items. These are unavoidable in a large information source, but reducing their number would be useful. There are also ontological errors, including confusion between instances and subclasses. Ontological errors cause severe problems when using Wikidata as a Knowledge base as one error generally affects much information.
The ontology in Wikidata is very complex and not well organized, particularly in its upper levels, where there can be several related classes, resulting in different classes being used in different areas of Wikidata. There are also multiple related properties, again with different properties being used in different areas. To exploit Wikidata information in a knowledge base, consumers need to know which class or property is used in each area, limiting general-purpose use.
There is no formal meaning for Wikidata. Consumers need to guess the intent of many classes and properties from very limited descriptions. This is particularly problematic for temporal qualifiers. A stronger formal theory would be the basis for better guidance to contributors on how to enter new information in Wikidata.
The constraint mechanism does help to identify several kinds of errors. However, constraints are very weak as they only point out potential problems. Some mechanism to exclude constraint violations would be useful. Further, the poor ontology organization makes it difficult to write good constraints. Constraints that are prescriptive and that can actually affect Wikidata would aid in its use as knowledge.
But what is most needed to make Wikidata more useful as general information is a tightening of the ontological modelling in Wikidata, including at least a much better description of its major classes and properties and how information combines in it. Then a formal theory for Wikidata data could be developed, permitting strong tools that can find and fix errors in Wikidata and tie together information from different parts of Wikidata. Strong tools can also discover information implicit in Wikidata and make this information available for use.

Hopefully, a group of Wikidata contributors will form to produce better ontological modelling in Wikidata and produce a formal theory for Wikidata. To help, the Wikidata community could set up mechanisms to encourage fixing problems in Wikidata information over just adding new information.

Talk ID
wikidatacon2019-1101
Event:
wikidatacon2019
Day
2
Room
Einstein
Start
2:30 p.m.
Duration
00:25:00
Track
None
Type of
Talk
Speaker
Peter F. Patel-Schneider
100.0% Checking done100.0%
0.0% Syncing done0.0%
0.0% Transcribing done0.0%
0.0% Nothing done yet0.0%