< Home
Logo

Create
TitleCategoryDescriptionCreated atMaintainer

21-24 / 24 show all
KO TGM 2016Template generation Description SenTGM is a SRDF-based Korean Template Generation module for generating SPARQL template from natural language question. SPARQL template follows 'templator' module made by christina unger. Function 1. Translate natural language question to declarative sentence by rules. 2. Run SRDF module for this declarative sentence. 3. Convert SRDF output to SPARQL template. Scope and Limit Translating NLQ to DS is developed very simple. If translate-sub-module is developed better, the overall performance will be raise. References 1. Sangha Nam, et. al., "SRDF: Korean Open Information Extraction using Singleton Property", ISWC (Poster) 2015.2016-07-21 02:26:02 UTCnam.sangha@gmail.com
Korean DMDisambiguation # Description Korean DM is the first version of Korean Disambiguation Module. It uses pre-defined attributes and ELU to disambiguate property & entities # Function Korean DM find corresponding entities and properties from the output of TGM. Based on the given information it tried to find the best matching for verbalized variables. The result is returned as three categories (properties / classes / entities) with its variables. # Scope and limit Korean DM only disambiguates properties and entities. It does not work for finding correct classes at the moment. The program would be updated to handle lexicaly associated properties, and filter properties that could not make result according to the given template # Language Dependency It only supports Korean text. (July 21, 2016, OKBQA4). Maintainer: Jeong-uk Kim {prismriver@kaist.ac.kr}2016-07-21 05:01:15 UTCprismriver@kaist.ac.kr
Controller 2016Control Main changes Extended configuration The arbitrary number of module can be configured. The sequence of modules executed can be configured. A KB address can be configured with a tuple of KB address and graph IRI. Example: https://sites.google.com/site/okbqa4/development/documentation/controller?pli=1 The form of log messages Every output of each module is co-printed with its input. Each log of each module is printed with sorting. Processing times of each module are noticed. Exception messages are simplified. Example: https://sites.google.com/site/okbqa4/development/documentation/controller?pli=1 Asynchronous logging and processing The controller is changed so that the web interface can receive and print log messages and result of the controller asynchronously via the mysql database located in the okbqa server. If you do not specify the "sync" field on the "conf" field of the input json, the controller will return immediately with "rid" value, which is the record ID of a controller's log messages and result written asynchronously on the mysql database. If you specify the "sync" field as "on" value (see the sample input below), the controller will operate in the previous manner that returns log messages and results for an input json, synchronously. Limitations Query processing speed (Now resolved) There are a lot of SPARQL queries produced, which causes the entire processing time of the pipeline. One of solutions can be to filter out the queries with scores under a threshold. To do so, a controller should be able to deal with module-scores properly. 2016-08-08 06:00:04 UTCjiseong@kaist.ac.kr
Answerer 2016Answer generation Main changes It is slightly changed to coherent to controller 2016. Some optimization has been adapted. Limitations Query processing speed (Now resolved) Not yet, AGM 2016 uses scores to prune SPARQL queries to reduce the search space. Currently, the processing time of the entire pipeline is the one of the main issues. In the next version, it can be considered to use of scores to boost up the processing speed. 2016-08-08 06:00:32 UTCjiseong@kaist.ac.kr
Create