Vulcan/TextualEvidence/Plan

9/5/2013

The plan from here is:

1. Get a simple system running which can take input in the form of
   1. an input proposition triple (arg1, rel, arg2) and return a ranked list of tuples from the texts already indexed. Ranking will be still be crude (either lucene or extraction confidence scores). See Scoring for the plan on how to score eventually.
   2. a keyword query, which will return indexed tuples matching the keyword(s) queried. This is mostly as a tool for exploring the indexed data.

It would be nice to have a minimal web-frontend to this.

1. Get some examples of queries generated from proposition tuples for the kinds of query templates we expect to use to try to find evidence, along with some results for some example queries. See QueryGeneration for details on the kinds of queries that we'll generate and how.
2. Define the Tuple representation the system will use in code. This'll be commonly used, so we want to settle on a definition early for people to be able to build with.
3. Add support for working with lexical variants of tuple terms where appropriate in the indexed tuple store and in the runtime query generation, execution, and scoring layer. This includes
   1. lemmatization
   2. head word extraction
   3. polarity extraction
   4. synonym expansion