The following list of integration rules shows, for each instance of an event class in the organized crime conceptual graph (in bold), the corresponding representation in RDF that it would have in FrameBase. In particular, the main event instance is represented by the anonymous node _:e. The default prefix indicates elements that already existed in the core FrameBase schema created from FrameNet and WordNet.
•Event _:e a :frame-Event-event.n
•Act _:e a :frame-Intentionally_act-act.n
•Arrest _:e a :frame-Arrest-arrest.n
•Drug Possession Arrest _:e a :frame-Arrest-arrest.n . _:e :fe-Arrest-Offense _:e2 .
_:e2 a :frame-Offenses-possession.n
•Human Trafficking Arrest _:e a :frame-Arrest-arrest.n . _:e :fe-Arrest-Offense _:e2 .
_:e2 a :frame-Commerce_scenario-trafficker.n .
_:e2 :fe-Commerce_scenario-Goods :frame-People-human.n
•Metal Theft Arrest _:e a :frame-Arrest-arrest.n . _:e :fe-Arrest-Offense _:e2 .
_:e2 a :frame-Theft-theft.n .
_:e2 :fe-Theft-Goods :frame-Substance-metal.n . _:e2 a :frame-Offenses-theft.n
•Buy _:e a :frame-Commerce_buy-buy.v
•Crime _:e a :frame-Committing_crime-crime.n
•Illegal Drug Use _:e a :frame-Ingest_substance-use.v
•Consume _:e a :frame-Ingestion-consume.v
•Inhale _:e a :frame-Ingest_substance-sniff.v
•Inject _:e a :frame-Ingest_substance-inject.v
•Possession _:e a :frame-Offenses-possession.n
•Smoke _:e a :frame-Ingest_substance-smoke.v
•Organised Crime
Paper C.
•Theft _:e a :frame-Theft-theft.n . _:e a :frame-Offenses-theft.n
•Metal Theft _:e a :frame-Theft-theft.n . _:e :fe-Theft-Goods :frame-Substance-metal.n . _:e a :frame-Offenses-theft.n
•Trafficking _:e a :frame-Commerce_scenario-trafficker.n
•Drug Trafficking _:e a :frame-Commerce_scenario-trafficker.n . _:e :fe-Commerce_scenario-Goods :frame-Intoxicants-drug.n
•Human Trafficking _:e a :frame-Commerce_scenario-trafficker.n . _:e :fe-Commerce_scenario-Goods :frame-People-human.n
•Seizure _:e a :frame-Taking-seizure.n
•Drug Seizure _:e a :frame-Taking-seizure.n . _:e :fe-Taking-Theme :frame-Intoxicants-drug.n
•Sell _:e a :frame-Commerce_sell-sell.v
•Transaction _:e a :frame-Commercial_transaction-transaction.n
•Crime Transaction _:e a :frame-Commercial_transaction-transaction.n .
_:e a :frame-Committing_crime-crime.n
•Drug Trafficking Transaction
_:e a :frame-Commercial_transaction-transaction.n . _:e a :frame-Committing_crime-crime.n .
_:e :fe-Commercial_transaction-Goods :frame-Intoxicants-drug.n
•Human Trafficking Transaction
_:e a :frame-Commercial_transaction-transaction.n . _:e a :frame-Committing_crime-crime.n .
_:e :fe-Commercial_transaction-Goods :frame-People-human.n
•Metal Theft Transaction
_:e a :frame-Commercial_transaction-transaction.n . _:e a :frame-Committing_crime-crime.n .
_:e :fe-Commercial_transaction-Goods :frame-Substance-metal.n
The hierarchy in the original ontology is not necessarily consistent with the hierarchy in FrameBase. Only in certain cases does a superclass relationship between two elements of the source also exist between the two elements’ respective translations to FrameBase. Therefore, for each translation of an original class of event, the translations of the parents in the original ontology can be added to the set of instances (ABox) in FrameBase, and this will provide additional knowledge that would not always be inferred by the FrameBase schema alone.
We minimize the need for declaring new frames and frame elements for specialized domains by making use of the compositionality of most specialized terms, creating complex structures that combine the semantics of simpler, basic elements. For instance, the translation for the event of type “Drug Possession Arrest” declares an event of type arrest, and specifies that it is about drug possession by assigning drug possession (Offenses-possession.n) as the offence.
4. Integrating Events
Owing to this flexibility, we merely needed to mint one single new en- tity that had not existed in the core FrameBase schema (the microframe Organization-criminal%20organization.n, with the prefix fbe: denoting that this is an extension). This exemplifies the potential of FrameBase to rep- resent events from relatively specialized domains, but at the same time the capacity to be extended to fill any possible gaps.
For representing timelines, the frame Individual_history-history.n can be used. Each timeline can be represented with one instance of that frame. This instance can be linked with the frame element Individual_history-- Domainto the topic, which is preferably an entity (or alternatively, a literal or an anonymous node or dummy entity named with a literal). The instance can also be linked with the frame element Individual_history-Event to each of the elements in the timeline. Additional frame elements are available in FrameBase, originating from FrameNet, for expressing participants, total duration, etc.
Then, complex queries such as retrieving all events in a given timeline between two given dates, can be built in SPARQL. Similarly, sub-events can be represented with the property path: ^:fe-Part_whole-Part/:fe-- Part_whole-Whole.