2015 DeRiVE FrameBase event integration presentation

Representing Specialized Events with FrameBase

Jacobo RoucesAalborg University

[email protected]

Gerard de MeloTsinghua [email protected]

Katja HoseAalborg [email protected]

06/01/15 Rouces, De Melo, Hose – FrameBase 2

Overview

● FrameBase

● Integration of events: Dbpedia

● Integration of events: schema.org

● Integration of event aspects

● Complexity

● Representional flexibity

● Conclusions


FrameBase: motivation

● Different KBs use different ways to represent N-ary relations– Using Direct Binary Relations

● Used as “default” mode in most KBs. Dereified.

– RDF reification● YAGO,YAGO2s

– Subproperties● Proposed in [Nguyen et al, WWW 2014]

– Neo-davidsonian representations● To an extent used in most Kbs that include events. E.g. Freebase

● Difficult to link (no equivalence relations) and to query.


FrameBase: schema

● Core: RDFS schema to represent knowledge using neo-Davidsonian approach with a wide and extensible vocabulary of

– frames (events, situations, frames, eventualities…)

– frame elements (outgoing properties representing frame-specific semantic roles)

● Vocabulary based on NLP resources (FrameNet+WordNet) – This provides connection with natural language and semantic role labeling

systems (e.g. detect events with SEMAFOR). Cluster near-equivalents.

● Inference rules to provide direct binary predicates?f a :frame-Separating-partition.v ?f :fe-Separating-Whole ?s ?s :isPartitionedIntoParts ?o?f :fe-Separating-Parts ?o


FrameBase: schema

e1Frame type

e2

e3

FRAME CLASS

FRAME ELEMENT(FRAME-SPECIFIC SEMANTIC ROLES)

FRAME INSTANCEDIRECT BINARY PREDICATE


FrameBase: ReDer rules

● Two-layered structure:

☞Create two levels of reification, and reification-dereification (ReDer) inference rules that connect them.

● Reified knowledge using frames and frame elements● Dereified knowledge using direct binary predicates

– Rules are Horn clauses (good for inference engines)

e1Event type

e2

e3

?f a :frame-Separating-partition.vAND?f :fe-Separating-Whole ?sAND?f :fe-Separating-Parts ?oIFF?s ..-isPartitionedIntoParts ?o


FrameBase: example

yago:Nobel_Prize

...-competitor

yago:Nobel_Prizeyago:Nobel_Prize

fe-Win_prize-competition fe-Win_prize-prize

1921^xsd:date

...-time ...-explanation

BEYOND TIME AND LOCATION!


FrameBase: example

:frame-Win_prize-win.v

...-competitor

yago:A_Einsteinyago:Nobel_Prize


1921^xsd:date

...-time

yago:Photoelectric_effect

...-explanation

frame:Working_on-work.n

fe-Working_on-agent

...-domain

...-time

1905^xsd:date



FrameBase: example


...-competitor



1921^xsd:date

...-time

?

??


...-explanation


fe-Working_on-agent

...-domain

...-time

1905^xsd:date

?



FrameBase: example


...-competitor



1921^xsd:date

...-time

winsByCompetitor

winsAtTime isWonAtTime


...-explanation


fe-Working_on-agent

...-domain

...-time

1905^xsd:date

worksAtTime



FrameBase: ReDer rules

● FrameBase: Two-layered structure:

☞Create two levels of reification, and inference rules that connect them.

● Reified knowledge using frames and frame elements● Dereified knowledge using direct binary predicates

– Rules are Horn clauses (good for inference engines)

– Around 15000 rules and direct binary predicates are created automatically.

– Different storage strategies are possible.

?f a :frame-Separating-partition.vAND?f :fe-Separating-Whole ?sAND?f :fe-Separating-Parts ?oIFF?s ..-isPartitionedIntoParts ?o


FrameBase: integration rules

● Integration rules from source KBs can be created with SPARQL CONSTRUCT queries (and optionally a RDFier)

CONSTRUCT { _:e a framebase:frame-People_by_jurisdiction-citizen.n . _:e framebase:fe-People_by_jurisdiction-Person ?person . _:e framebase:fe-People_by_jurisdiction-Jurisdiction ?country .} WHERE { ?person freebase:people.person.nationality ?country . }

● More examples in the ESWC 2015 paper “FrameBase: Representing N-ary Relations Using Semantic Frames”


Integration of events


Integration of events: DBpedia#For sub-classes of dbpedia-owl:EventCONSTRUCT { ?e a :frame-Social_event-meeting.n .} WHERE {?e a dbpedia-owl:SocietalEvent}

#For sub-classes of dbpedia-owl:SocietalEventCONSTRUCT { ?e a :frame-Project-project.n . ?e :fe-Project-Activity dbpedia:Space_exploration .} WHERE {?e a dbpedia-owl:SpaceMission}

#For sub-classes of dbpedia-owl:SocietalEventCONSTRUCT { ?e a fbe:frame-Social_event-convention.n .} WHERE {?e a dbpedia-owl:Convention}

SHOULD MATCH THE SUPERCLASS RULE TOO


Integration of events: DBpediaCONSTRUCT { ?e a :frame-Event-event.n . ?e :fe-Event-Time _:timePeriod . _:timePeriod a fbe:frame-Timespan-period.n ; fbe:fe-Timespan-Start ?o1 ; fbe:fe-Timespan-End ?o2 . _:e2 a :frame-Relative_time-preceding.a ; :fe-Relative_time-Landmark_occasion ?e ; :fe-Relative_time-Focal_occasion ?o3 . _:e3 a :frame-Relative_time-following.a ; :fe-Relative_time-Landmark_occasion ?o3 ; :fe-Relative_time-Focal_occasion ?e . _:e4 a :frame-Relative_time-following.a ; :fe-Relative_time-Landmark_occasion ?e ; :fe-Relative_time-Focal_occasion ?o4 . _:e5 a :frame-Relative_time-preceding.a ; :fe-Relative_time-Landmark_occasion ?o4 ; :fe-Relative_time-Focal_occasion ?e . ?e :fe-Event-Reason ?o5 . ?e a :frame-Social_event-meeting.n ; :fe-Social_event-Attendee ?o8 .} WHERE { ?e a dbpedia-owl:Event . OPTIONAL{?e dbpedia-owl:startDate ?o1} OPTIONAL{?e dbpedia-owl:endDate ?o2} OPTIONAL{?e dbpedia-owl:previousEvent ?o3} OPTIONAL{?e dbpedia-owl:followingEvent|dbpedia-owl:nextEvent ?o4} OPTIONAL{?e dbpedia-owl:causedBy ?o5} OPTIONAL{?e dbpedia-owl:duration ?o6} OPTIONAL{?e dbpedia-owl:numberOfPeopleAttending ?o7} #Omitted OPTIONAL{?e dbpedia-owl:participant ?o8} }


Integration of events: schema.orgCONSTRUCT { ?e a :frame-Social_event-meeting.n . ?e :fe-Social_event-Time _:timePeriod . _:timePeriod a fbe:frame-Timespan-period.n ; fbe:fe-Timespan-Start ?Osta ; fbe:fe-Timespan-End ?Oend . ?e :fe-Social_event-Duration ?Odur . ?e :fe-Social_event-Place ?Oloc . ?e :fe-Social_event-Attendee ?Oatt . ?e :fe-Social_event-Host ?Oorg . ?e :fe-Social_event-Occasion ?Osup . ?Osub :fe-Social_event-Occasion ?e . ?Ooff a :frame-Offering-offer.v ; :fe-Offering-Theme ?e . ?e a :frame-Performing_arts-performance.n ; :fe-Performing_arts-Performer ?Oper ; :fe-Performing_arts-Performance ?Owor . _: a :frame-Recording-record.v ; :fe-Recording-Phenomenon ?e ; :fe-Recording-Medium ?Orec .} WHERE { ?e a sch:Event . # Unambiguous translation OPTIONAL{?e sch:startDate ?Osta} OPTIONAL{?e sch:endDate ?Oend} OPTIONAL{?e sch:duration ?Odur} OPTIONAL{?e sch:location ?Oloc} OPTIONAL{?e sch:attendee ?Oatt} OPTIONAL{?e sch:organizer ?Oorg} OPTIONAL{?e sch:superEvent ?Osup} OPTIONAL{?e sch:subEvent ?Osub} OPTIONAL{?e sch:offers ?Ooff} OPTIONAL{?e sch:performer ?Oper} OPTIONAL{?e sch:workPerformed ?Owor} OPTIONAL{?e sch:recordedIn ?Orec} # Ambiguous translation OPTIONAL{?e sch:doorTime ?Odoo} # No translation OPTIONAL{?e sch:eventStatus ?Oeve} OPTIONAL{?e sch:typicalAgeRange ?Otyp} OPTIONAL{?e sch:previousStartDate ?Opre} }


Integration of event aspects● Time and space:

– Frame elements ...-Time and ...-Place:fe-Social_event-Place

:fe-Social_event-Time

:fe-Competition-Place

:fe-Competition-Time

:fe-Smuggling-Place

:fe-Smuggling-Time

...


Integration of event aspects● Participation

– Frames include participants like agents, patients, etc.:fe-Commerce_buy-Buyer → :fe-Getting-Recipient

:fe-Destroying-Destroyer → :fe-Transitive_action-Agent

:fe-Destroying-Undergoer → :fe-Transitive_action-Patient


Integration of event aspects● Relations between events

– Mereology (part of)● Using a suitable FE, when available (see example):

?whole :fe-Social_event-Occasion ?part

● Or using one frame and 2 FEs:_:i a :frame-Part_whole ._:i :fe-Part_whole-Part ?part ._:i :fe-Part_whole-Whole ?whole .

● Both options can be used


Integration of event aspects● Relations between events

– Causality (cause of)● Using a suitable FE, when available (see example):

?consequence :fe-Event-Reason ?cause

● Or using one frame and two FEs:_:i a :frame-Causation ._:i :fe-Causation-Cause ?cause ._:i :fe-Causation-Effect ?consequence .

● Both options can be used

– Correlation (share common cause)● Instantiate a common cause using the methods above


Integration of event aspects● Documentation

– Events can be “documented using some media like photos or videos captured during the event” (Scherp and Mezaris 2014)

– Using the frame Recording with an available lexical unit (like recording.v) or an extension:

_:i a :frame-Recording-record.v .

_:i :fe-Recording-Phenomenon ?event .

_:i :fe-Recording-Medium ?media .

Medium is the physical entity in which the Agent creates a record of their impression of the Phenomenon.

In fact, Pepys recorded everything in his diary.


Integration of event aspects● Interpretation

– Very broad definition: “capturing subjectivity that may exist on the other aspects of events” (Scherp and Mezaris 2014)

● Using perspectivization from FrameNet

:frame-Commerce_sell → :frame-Commerce

:frame-Commerce_buy → :frame-Commerce

● Using extra frame, e.g.:

_:i a :frame-Becoming_Aware .

_:i :fe-Becoming_Aware-Cognizer ...

_:i :fe-Becoming_Aware-Instrument …

_:i :fe-Becoming_Aware-Means ...

_:i :fe-Becoming_Aware-Phenomenon ...

The Cognizer is the person who becomes aware of a PhenomenonPat discovered a great little restaurant in Soho.

The Cognizer uses an Instrument to (enable themselves to) become aware of the Phenomenon.

Olson says the deputy came out to the farm and detected a radioactive substance with his Geiger counter.


Complexity● Basic structure of integration rule

SOURCE FRAMEBASE

Event Frame class

Outgoing property 1 Frame element 1

Outgoing property 2 Frame element 2

... ...

Outgoing property n Frame element n


Complexity● Deviations: several frames instantiated

SOURCE FRAMEBASE

Event Frame class 1 ... Frame class n

Outgoing property 1 Frame element 1,1 ... Frame element 1,n

Outgoing property 2 Frame element 2,1 .. Frame element 2,n

... ... ... ...

Outgoing property n Frame element n,1 .. Frame element n,n


Complexity● Deviations: frame elements inverted

SOURCE FRAMEBASE

Event Frame class

Outgoing property 1 Frame element 1 ^Frame element 1

Outgoing property 2 Frame element 2 ^Frame element 2

... ... ...

Outgoing property n Frame element n ^Frame element n


Complexity● Deviations: property in source (reification)

SOURCE FRAMEBASE

Property Frame class

Frame element 1

Frame element 2

...

Frame element n


Complexity● All these deviations, and possibly others,

can be combined


Representational flexibility● Two ways of “narrowing down”

– New lexical unitX a :frame-Statement-twit.n

– Assign a value to a frame elementX a :frame-Statement-write.v

X :fe-Text_creation-Place dbpedia:Twitter


Representational flexibility● Further reification

– Remember different options for mereology, causality, interpretation...

– Even for participation: There is a frame Participation

– It boils down to the fact that FEs can be reified (substituted by a frame instance and two FEs), and sometimes FrameNet/FrameBase have only one option and sometimes have both.

– Possible solution: further reification-dereification rules?


Conclusions● FrameBase offers wide-range, natural-language-related

and extensible schema for representation of events and more...

● But automatic creation of rules remains a challenge:

– But rules are complex, which makes any training space very sparse, which makes difficult to train any system to create them automatically.

– Still some heterogeneity


Data

● More information: http://framebase.org

● Data is open-source. – License: CC-BY 4.0 International

The research leading to these results has received funding from the European Union Seventh Framework Programme (FP7/2007-2013) under grant agreement No. FP7-SEC-2012-312651 (ePOOLICE project).

Additional funding was provided by National Basic Research Program of China Grants 2011CBA00300, 2011CBA00301, and NSFC Grants 61033001, 61361136003.

http://framebase.org/


Questions

2015 DeRiVE FrameBase event integration presentation

Internet

Transcript of 2015 DeRiVE FrameBase event integration presentation