Difference between revisions of "Vulcan/MeetingNotes/Sep13 2013"

From Knowitall
Jump to: navigation, search
(Update)
(Update)
Line 19: Line 19:
 
</blockquote>
 
</blockquote>
 
:3. Update the system architecture figure to emphasize textual matching using procedural escapes. [Niranjan, Done.]
 
:3. Update the system architecture figure to emphasize textual matching using procedural escapes. [Niranjan, Done.]
 +
<blockquote>
 +
* See [[Vulcan/SystemStatus#Inference]].
 +
</blockquote>
  
 
4. Definition processing -- Stephen has been analyzing and adding to his patterns based on a larger sample of definitions.
 
4. Definition processing -- Stephen has been analyzing and adding to his patterns based on a larger sample of definitions.

Revision as of 06:53, 13 September 2013

Update

System Dev. To Do
1. Convert current prototype into a working system.[Niranjan: Not ready yet. In progress].
  • Implemented dynamic predicates (i.e. predicates don't have to be fully materialized within Tuffy's databases).
  • Actual evidence is being selected for each proposition (though not through Textual Evidence Finder)
  • Rules being used are fed in Tuffy format.
  • Stemming/Headwords and Synonym transforms need to be added.
  • Integrate closely with Textual evidence finder.
  • Finish system building and have system output be evaluated by Vulcan evaluation frame work. Revised ETC Sept 18th.
2. Textual evidence finder [Greg]
  • minimal web interface [Done!]
  • tuple representation design [Done!!]
  • lexical variants (head word, stemming etc.) [In progress?]
3. Update the system architecture figure to emphasize textual matching using procedural escapes. [Niranjan, Done.]

4. Definition processing -- Stephen has been analyzing and adding to his patterns based on a larger sample of definitions.

  • Key issue is in determining what form the output should take to facilitate inference.
  • Niranjan needs to look at examples from Stephen's output to see if the current design fits.
Points of integration
1. Add UW folks to e-mail list [Peter, done.]
2. Make a single wiki at Vulcan. Move UW's content to the new wiki. [Niranjan will work with Wil Smith. Status?]
3. Integrate w/ Vulcan testing framework. [Niranjan: UW's inference system will be a web service that outputs the reqd xml.]
4. Training data [Niranjan will work with Peter to make sure all data is available at UW.]
5. Share URLs for demos and services at Vulcan [Peter]
6. Send information about various knowledge sources inside vulcan [Peter]
7. Send Stephen pointers about dicitionary processing. [Peter, done.]