< Home
Logo

Create
TitleCategory DescriptionCreated atMaintainer

21-24 / 24 show all
Controller 1.2.0Control Description It is an implementation of the control module on the OKBQA architecture. The module gets question, language, and configuration as an input (JSON format) and returns the output (JSON format) with a list of answers corresponding to the input question with SPARQL queries for getting the answers. Each modules for being used to answer the question can be configured by giving the "conf" field of the input JSON. The example is shown right below. { "string": "Which rivers flow through Seoul?", "language": "en", "conf": { "tgm": ["tgm_address_1", "tgm_address_2", ..., "tgm_address_a"], "dm": ["dm_address_1", "dm_address_2", ..., "dm_address_b"], "qgm": ["qgm_address_1", "qgm_address_2", ..., "qgm_address_c"], "agm": ["agm_address_1", "agm_address_2", ..., "agm_address_d"], "kb": ["kb_address_1", "kb_address_2", ..., "kb_address_e"], "graph_uri": "graph_uri_1", "timelimit": time_limit } } The value of the "timeout" field limits the responding time of each module. If configuration is not provided, the default configuration will be used. The default setting of the configuration is as follows: { "conf": { "tgm": ["http://121.254.173.77:1555/templategeneration/templator/"], "dm": ["http://121.254.173.77:2357/agdistis/run"], "qgm": ["http://121.254.173.77:38401/queries"], "agm": ["http://121.254.173.77:7744/agm"], "kb": ["http://dbpedia.org/sparql"], "graph_uri": "", "timelimit": 10 } } The implementation returns not only answers, but also log messages can be useful for debugging each module by developers. The implementation fully support concurrency control as well. Scope and limit This implementation is an almost initial version of a control module, so there are many functionalities can be added to the implementation. The implementation provides only limited configuration fields in an input JSON, e.g., only addresses of each module. There can be many configuration fields that can be useful for the entire pipeline to be efficiently tested. Currently, KB addresses and a graph URI can be configured independently, which could be undesirable for users who want to specify graph URIs for each KB. It will be revised in the next version of the implementation. 2016-03-05 08:34:52 UTCjiseong@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 2014Answer generation Description It is an implementation of the answer generation module on the OKBQA architecture. The module gets a list of SPARQL queries as an input (JSON format) and returns the output (JSON format) with a list of answers with their source SPARQL query. The number of returned answers and the time interval (seconds) of SPARQL querying can be configured by GET parameters; an example is shown below. http://ws.okbqa.org:7744/agm?answer_num=5&query_interval=0.1 If configuration is not provided, the default configuration will be used. The default setting of the configuration is as follows: { "conf": { "answer_num": 5, "query_interval": 0.0 } } Scope and limit This implementation is an initial version of an answer generation module, so there are many functionalities can be added to the implementation. The implementation provides only limited configuration fields in an input JSON, the number of answers to be returned and the interval time of SPARQL querying. There can be many configuration fields that can be useful for the entire pipeline to be efficiently tested. 2016-03-05 08:34:24 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