Upload
filip-ilievski
View
182
Download
0
Embed Size (px)
Citation preview
Streaming event architecture
Piek, Filip
NAFs
NAF2SEM
- chunk size- map non-entities?- location of frame files...
Extraction arguments
Cross-documentEvent
Coreference
- match type- needed roles- synsets or phrases- time(for each event type)
Matching arguments
Knowledge Store
#1) NAF2SEM
● reads NAFs as they come● extracts events within a single file● converts them to RDF-TRIG● passes the RDF relations to the cross-document Event
Coreference module
#2) Event Coreference module
● gets a stream of RDF events● for each event, checks if coreferential event exists in KS
○ yes => insert event RDF + identity relations (to other events) in KS○ no => insert event RDF only
#3) Knowledge Store
● exposes a method to insert RDF from outside● merges events which are connected with an identity relation
This means ..
● .. now we have a streaming end-to-end architecture, from NAF to KS
● .. no need to reprocess previous NAFs when new file arrives● .. flexibility and support for further event coreference research
○ new idea =>adjust the command line arguments
● .. the NAFs should be processed in decent chunks to prevent crashing KS
Future brings ..
.. cool ideas (to be examined first):
● using WordNet relations for coreference● handling future events● specific treatment for recent events which happened in the last
X days
DEMO
New NAF arrived
NAF2SEM creates TRIG
EC queries the KS for potential matches
example query:
Event types
Associated ILIs
Role fillersTime expressions
.. and appends identity relations to the TRIG file
The TRIG is now ready to be digested by KS.