GATE track 1 session: Difference between revisions

From zooid Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Wiki_List |
A full week of learning [http://en.wikipedia.org/wiki/General_Architecture_for_Text_Engineering GATE] text mining/information extraction language processing and talks. [http://gate.ac.uk/wiki/TrainingCourseAug2010/ Session wiki]
wiki_name  =                ComposerPlanet                                          |
 
wiki_logo =                  [[Image:NoLogo.png]]                                   |
[[File:GATE_screenshot.png|900px|GATE developer screenshot]]
wiki_URL =                 http://composerplanet.com/                                                                       |
 
wiki_recentchanges =       http://www.composerplanet.com/cgi-bin/wiki.cgi?RecentChanges                                      |
GATE is written in Java and very Java centric. This makes it portable, fast, and heavyweight. A programming library is available.  It's 14 years old and has many users and contributors.
wiki_status =               Active                    |
 
wiki_lastreviewed =       16-Jan-06                  |
= Using GATE developer =
wiki_language =             English                    |
 
wiki_editmode =             OpenEdit            |
* GATE developer is used to process sets of Language Resources in Corpus using Processing Resources. They are typically saved to a serialized Datastore.
wiki_engine =               Unknown                        |
* ANNIE, VG (verb group) processors.
wiki_maintopic =            Music
* Preserve formatting embeds tags in HTML or XML.
}}
** Different strengths using GATE's graph (node/offset) based XML vs. preserved formatting (original xml/html)
==Description==
 
Deals with aspects of music and composing
= Information Extraction =
 
* IR - retrieve docs
* IE - retreive structured data
 
* Knowledge Engineering - rule based
* Learning Systems - statistical
 
Old Bailey IE project  - 17th century english (Online)
 
* POS - assigned in Token (noun, verb, etc)
 
* Gazateer - gotcha, have to set initialization parameter listsURL before it's loaded. Must also "save and reinitialize."
* Gazeteer creates Lookups, then transducer creaties named entities
* Then orthomatcher (spelling features in common) coreference associates those
 
* Annotation Key sets and annotation comparing
** Need setToKeep key in Document Reset for any pre annotated texts
 
== Evaluation / Metrics ==
 
* Evaluation metric - mathematically against human annotated
* Scoring - performance measures for annotation types
 
* Precision = correct / correct + spurious
* Recall = correct / correct + missing
* F-measure is precision and recall (harmonic mean)
* F=2⋅(precision⋅recall / precision+recall)
* GATE supports average, strict, lenient
 
* Result types - Correct, missing, spurious, partially correct (overlapped)
 
* Tools > Annotations Diff - comparing human vs machine annotation
 
* Corpus > Corpus quality assurance - compare by type
* (B has to be the generated set)
 
* Annotation set transfer (in tools) - transfer between docs in pipeline
** useful for eg HTML that has boilerplate
 
 
== To investigate ==
 
* markupAware for HTML/XML (keeps tags in editor)
* AnnotationStack
* Advanced Options
 
= JAPE =
 
* Rules based on tokens and lookups
 
Phase: MatchingStyles
Input: Lookup
Options: control = appelt
Rule: Test1
(
({Lookup.majorType == location})?
{Lookup.majorType == loc_key}
):match
-->
  :match.Location = {rule=Test1}
 
Copying features: :match.Location = { type = :match.Lookup.minorType}
 
== To review, gotchas ==
 
* Rule types : first takes only first match, excludes compound
** a? b for "a b" will match "a b"
* multiplexor tranducers
* multi-constraint statements
* macros
* To reuse created annotations has to be a separate rule
 
=== Matching types ===
 
[[File:gate-matching.png|800px|Matching styles for JAPE]]
 
= To follow up =
 
* WebSphinx crawler CREOLE plugin
* [http://www.semanticsoftware.info/semantic-assistants-architecture GATE NLP web services]
 
= Other notes =
 
== Lucene data store and ANNIC ==
 
* Use <null> for default set
* Go to Datastore for queries
** eg {Person}({Token})+{Money}
* Useful for debugging JAPE and results
 
[[File:GATE-lucene-person-money.png|800px]]
 
= Demos =
 
* Mímir for querying large volumes of data (uses MG4J)
* Translating parts of speech between languages using Compound editor and Alignment editor
* Predicate extractor (MultiPaX)
** Mixed results at best
* OwlExporter
** NLP ontology
 
= Conclusions =
 
While it can do a lot out of the box and benefits from development time and breadth of connectivity, to be useful to more than patient specialists, it needs usability testing. A lot of things are inobvious and too domain specific that with a bit of work could be more broadly useful. Interaction could include a lot more immediate, useful and interesting looking displays. A web based version could have these features. However the team seems somewhat ambivalent about development. :)
 
Looking forward to learning about programming using GATE libraries.
 
{{Blikied|Aug 30, 2010}}
 
[[Category:SemWeb]]

Latest revision as of 01:10, 10 September 2010

The following wikis are powere by the ProWiki wiki engine.

The wiki homepage is : ProWiki.org

ProWiki development started in 2001 and since the it it used for wiki community projects at WIKISERVICE. It is GPLed in March 2006 to make it even more widely available.

Strength of the ProWiki engine:

  • the most flexible engine to build individual communities and to support different applicatzion needs from one code base
  • the ability to host and support many individual communities at one server (many cross-wiki abilities)
  • a very consistent and extendible architecture grown in long non-GPL development period