1 / 13

Combining GATE and UIMA

Explore the interoperability between GATE and UIMA, including mapping annotations, feature structures, and processing units. Learn how to seamlessly combine the two frameworks with examples, demos, and mapping instructions.

vegad
Download Presentation

Combining GATE and UIMA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Combining GATE and UIMA Ian Roberts

  2. Overview • Introduction to UIMA • Comparison with GATE • Mapping annotations between GATE and UIMA • Examples and demo

  3. What is UIMA? • Language processing framework developed by IBM • Similar document processing pipeline architecture to GATE • Concentrates on performance and scalability • Supports components written in different programming languages (currently Java and C++) • Native support for distributed processing via web services

  4. UIMA Terminology • Processing tasks in UIMA are encapsulated in Analysis Engines (AEs) • Text-specific processing by Text Analysis Engines (TAEs) • In UIMA, AEs can be primitive (~ a single PR in GATE terms), or aggregate (~ a GATE controller). • Aggregate AE can include other primitive or aggregate AEs • GATE includes interoperability layer to run • GATE controller as a primitive TAE in UIMA • UIMA TAE (primitive or aggregate) as a GATE PR

  5. UIMA and GATE • In GATE, unit of processing is the Document • Text, plus features, plus annotations • Annotations can have arbitrary features, with any Java object as value • In UIMA, unit of processing is CAS (common analysis structure) • Text, plus Feature Structures • Annotations are just a special kind of FS, which includes start and end offset features

  6. Key Differences • In GATE, annotations can have any features, with any values • In UIMA, feature structures are strongly typed • Must declare what types of annotations are supported by each analysis engine • Must specify what features each annotation type supports • Must specify what type feature values may take • Primitive types - string, integer, float • Reference types - reference to another FS in the CAS • Arrays of the above • All defined in XML descriptor for the AE

  7. Integrating GATE and UIMA • So the problem is to map between the loosely-typed GATE world and the strongly-typed UIMA world • Best explained by example…

  8. Example 1 • Simple UIMA annotator that annotates each instance of the word “Goldfish” in a document. • Does not need any input annotations • Produces output annotations of type gate.example.Goldfish

  9. Create UIMA doc Copy annotationsback Annotator adds annotation of type gate.example.Goldfish Add GATE annotation of type Goldfish at the corresponding place Example 1 UIMA GATE This is a document that talks about Goldfish… This is a document that talks about Goldfish… Goldfish Goldfish Run UIMA annotator

  10. We may want to copy annotations, as well as text, from the original GATE document. Consider a UIMA annotator that takes gate.example.Sentence annotations as input annotates “Goldfish” as before also adds a feature GoldfishCount to each Sentence giving the number of goldfish annotations in that sentence Example 2

  11. Create UIMA doc, with Sentence annotations Goldfish Goldfish Goldfish Goldfish … and also want tocopy new featureback to originalSentences Copy Goldfishannotations back… Run UIMA annotator, annotating Goldfish as before… numFish = 1 GoldfishCount = 1 …and adding a feature to each Sentence Example 2 GATE UIMA This is a document that talks about Goldfish. Goldfish are easy to look after, and … This is a document that talks about Goldfish. Goldfish are easy to look after, and … We need an index linking UIMA annotations to the GATE annotations they came from

  12. The mapping must be defined by the user in XML … create a UIMA annotation of this type at the same place… For each GATE annotation of type Sentence… … and remember this mapping Defining the mapping <uimaGateMapping> <inputs> <uimaAnnotation type="gate.example.Sentence" gateType="Sentence" indexed="true"/> </inputs>

  13. For each UIMA annotation of this type… For each UIMA annotation of this type… … create a GATE annotation at the same place … to the value of the GoldfishCount feature of the UIMA annotation. … find the GATE annotation it came from… … and set its numFish feature… Defining the mapping (2) <outputs> <added> <gateAnnotation type="Goldfish" uimaType="gate.example.Goldfish" /> </added> <updated> <gateAnnotation type="Sentence" uimaType="gate.example.Sentence"> <feature name="numFish"> <uimaFSFeatureValue name="gate.example.Sentence:GoldfishCount" kind="int" /> </feature> </gateAnnotation> </updated> </outputs> </uimaGateMapping>

More Related