Challenges in Chinese Knowledge Graph Construction

Challenges in Chinese Knowledge Graph Construction

Challenges in Chinese Knowledge Graph Construction Chengyu Wang, Ming Gao, Xiaofeng He, Rong Zhang* Shanghai Key Laboratory of Trustworthy Computing Data Science and Engineering Institute, East China Normal University 3663 North Zhongshan Road, Shanghai, China [email protected], fmgao,xfhe,[email protected] Abstract—The automatic construction of large-scale knowl- 1) The data sources in Chinese have quite different char- edge graphs has received much attention from both academia acteristics from English one. A number of online and industry in the past few years. Notable knowledge graph Chinese wikis are publicly available, such as Chi- systems include Google Knowledge Graph, DBPedia, YAGO, NELL, Probase and many others. Knowledge graph organizes nese Wikipedia, Baidu Baike (baike.baidu.com), Hudong the information in a structured way by explicitly describing the Baike (www.baike.com), etc. However, they differ in relations among entities. Since entity identification and relation data size and format; user generated tags and the extraction are highly depending on language itself, data sources data quality vary, too. Currently Chinese Wikipedia largely determine the way the data are processed, relations are contains only 0.8M articles, while Baidu Baike and extracted, and ultimately how knowledge graphs are formed, which deeply involves the analysis of lexicon, syntax and seman- Hudong Baike have over 10M, respectively. Knowledge tics of the content. Currently, much progress has been made for extraction and integration from these heterogeneous data knowledge graphs in English language. In this paper, we discuss sources poses greater challenge. the challenges facing Chinese knowledge graph construction 2) Resources for building Chinese knowledge graphs are because Chinese is significantly different from English in various limited. Some Chinese equivalents used as important linguistic perspectives. Specifically, we analyze the challenges from three aspects: data sources, taxonomy derivation and parts in English knowledge graph construction are not knowledge extraction. We also present our insights in addressing readily available. For instance, there are no public these challenges. knowledge repositories (e.g., Freebase.com) and seman- tic networks (e.g., WordNet) in Chinese for fact gener- I. INTRODUCTION ating and taxonomy building. Automatic construction of knowledge graph based on 3) Most information extraction algorithms ([9], [10]) are crowd-sourced data has attracted significant interest from both language-dependent. Chinese is different from English academia and industry due to its wide application in areas in vocabulary, semantics and grammar. For example, in like semantic search, machine reading and question answering. Chinese nouns there are no explicit singular/plural forms Projects such as DBPedia[1], YAGO[2], Kylin/KOG([3], [4]) which are used to detect conceptual entities in building and BabelNet[5] aim at building knowledge graphs by harvest- English knowledge graphs. New approaches are needed ing entities and relations from Wikipedia, one of the largest since it is doomed to fail if directly applying existing crowd-sourced, multilingual wikis on Web. Other projects, techniques to Chinese scenarios. such as NELL[6], TextRunner[7] and Probase[8], take more aggressive approach by extracting knowledge from unstruc- Motivated by these observations, we describe the research tured text in Web pages. challenges in Chinese knowledge graph construction in fol- In the wide-spread mood of enthusiasm on knowledge lowing three aspects: (i) quality of data sources, (ii) taxonomy graph, we notice that its construction is quite language- derivation and (iii) knowledge harvesting. dependent. Data sources as well as the NLP or other methods In this paper, we discuss these challenges in details and with which to process the data are unique among languages, present our insights into them based on our practice. especially for those belonging to different language families. II. RESEARCH CHALLENGES Currently, most projects are concerning knowledge graph systems in English language. Because Chinese belongs to a A. Quality of Data Sources different language family, directly translating English knowl- Although Wikipedia is usually treated as high-quality data edge graphs into Chinese is not always feasible, hence Chinese source for many knowledge graphs such as YAGO and DBPe- knowledge graph construction is of great significance. dia, there are several quality issues in Chinese Wikipedia that In this paper, we focus on issues raised during Chinese should be paid special attention to. knowledge graph construction, discussing major challenges in 1) Data Sparsity: Wikipedia is a multi-lingual online this area. The significances of our paper are: encyclopedia. However, there exists a clear imbalance between * Corresponding author different language versions. There are over 4 million articles in 978-1-4799-8442-8/15/$31.00 © 2015 IEEE 59 ICDE Workshops 2015 English Wikipedia, while only about 0.8 million in Chinese. mechanisms should be developed to solve these problems. Fur- Furthermore, English Wikipedia contains 13 times more in- thermore, to address the sparsity issue, multiple data sources foboxes than Chinese Wikipedia[11]. The sparsity due to the can be considered together, each of which has confidence lack of infoboxes results in difficulty in knowledge harvest, scores indicating the level of correctness. Errors can be de- which can be denoted by following two questions: tected through various techniques such as entity integration • A lot of semantic relations between entities and entity [13] and reasoning-based methods. properties are missing. How can we construct a “dense” graph out of such data sources? B. Taxonomy Derivation • Chinese Wikipedia contains much fewer tail entities be- The taxonomy is the core of large-scale knowledge graphs in cause of the small number of wiki pages. How can we that it provides a hierarchical type system for entities. Ideally, design a mechanism that can identify the missing tail a taxonomy provides two types of relations: the subClassOf entities from other Web sources such that the knowledge relation between two classes and the instanceOf relation graph has high coverage? between a class and an entity. In a knowledge graph, every 2) Information Accuracy: In Web 2.0 era, most informa- entity e should belong to a class c indicating the type of tion on the Web is generated by Internet users. Inaccuracy the entity, represented as (e, instanceOf, c). A class can be a and errors are inevitable, and Wikipedia is not immune. For subclass of another class, or the root class itself. The goal of articles introducing professional knowledge, errors occur due taxonomy derivation is to identify such a hierarchical structure to the lack of expertise of the contributor. On the other of classes from data sources, thus plays an important role in hand, articles related to sensitive issues or events may be building knowledge graphs. written in favor of the contributor’s attitude. For instance, In wikis, the categories and their hierarchical structures can the page about PX (short for P-Xylene, a chemical material help derive the taxonomy, but these user-generated categories with toxicity slightly higher than ethanol) on Baidu Baike are often topical or thematic, rather than semantically tax- was modified back and forth tens of times with extremely onomic. The resulting problem is that the Wikipedia cate- different toxicity description, due to the polarized attitudes gory system does not provide a taxonomic structure between of the contributors towards the construction of a PX factory classes. We also found that many categories in other Chinese in city of Xiamen, China. Information extracted from pages wikis such as Baidu Baike only have the semantic associativity like this will certainly affect the correctness of the knowledge with the entity (i.e., relatedTo or topicOf ), instead of the strict graph. Attention should be paid to pages with high number instanceOf relation. For example, for Chinese president Xi of modifications while some attribute descriptions are quite Jinping, political leader is a valid class rather than politics or different from version to version. Sophisticated NLP methods China. will be required to accomplish this task. Intensive research has been conducted on English con- 3) Linking Quality: Wiki pages contain hyperlinks to tent. Because WordNet contains abundant semantic classes other wiki pages about entities appearing in anchor text. The and their relations, Suchanek et al.[2] combined the hy- link structure of these pages can be leveraged to construct pernymy/hyponymy relations in WordNet and facts derived semantic networks and perform tasks like entity linking[12]. from Wikipedia to generate taxonomy with high accuracy and In these scenarios, the link structure in Wikipedia serves as the coverage. In WikiTaxonomy[9], semantic relations between “gold standard” to provide support for other tasks. However, in categories are classified into isa and notisa relations through Chinese Wikipedia, we have identified many errors in links, in connectivity network and lexico-syntactic patterns. that the entity in anchor text is different from the target entity. Here is an example: the entity Wu Mei (a professor in Peking However, there are two challenges when trying to extract University) appeared in the page May Fourth Movement (a such information in Chinese language. First, there is no social and political

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    3 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us