Skip to content
ESA implementation using Wikiprep output
Java Python
Pull request Compare This branch is 4 commits ahead, 3 commits behind faraday:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
esa-lucene
README
addAnchors.py
addRedirects.py
directScan.py
lewis_smart_sorted_uniq.txt
readCatHier.py
scanCatHier.py
scanData.py
scanLinks.py
selected.txt
wiki_stop_categories.txt

README

Wikiprep-ESA

This is an effort to implement Explicit Semantic Analysis (ESA) as described in this paper:

"Wikipedia-based semantic interpretation for natural language processing"
2009, Gabrilovich, E. and Markovitch, S.

You can find this paper at: http://www.jair.org/media/2669/live-2669-4346-jair.pdf

Create a MySQL database 'wiki':
    mysql -u root -p
 
    CREATE DATABASE wiki;

This implementation consists of:
* scanLinks.py:
* scanData.py : that reads Wikiprep output into a MySQL database.
It creates "article","text" and "pagelinks" tables.

* addAnchors.py : that adds anchor text to target articles.
* addRedirects.py : that adds redirect text to target articles.

The scripts above are able to work on both Wikiprep legacy formats and modern format (as in Zemanta fork).

Evgeniy Gabrilovich provides a preprocessed dump for 5 November 2005 snapshot of Wikipedia English.

It is available at: http://www.cs.technion.ac.il/~gabr/resources/code/wikiprep/wikipedia-051105-preprocessed.tar.bz2

In its current settings, Python scripts of wikiprep-esa are ready to process this dump.
If you need to process dumps in formats of Zemanta, you need to set FORMAT in these scripts.

FORMAT can be following: "Gabrilovich", "Zemanta-legacy", "Zemanta-modern"

After reading preprocessed dump into the database and adding anchors and redirects, you need to use
"esa-lucene" to perform indexing.

* ESAWikipediaIndexer: performs indexing with Lucene by feeding it with article content from database.

* WikipediaNormalSearcher: at this step, you can use this class to perform a search in Lucene index.
keep in mind that at this point, the implementation won't be the same with Gabrilovich et al. (2009),
since cosine normalization is term-based in Gabrilovich et al. but document length based in Lucene.
Additionally, pruning is not yet applied in Lucene index as in Gabrilovich et al.

However, TF.IDF weighing scheme is the same (log-based) and is located in ESASimilarity class.

* IndexModifier: reads term frequency vectors from Lucene index and writes cosine-normalized TF.IDF values into
"tfidf" table in the database. This is done to apply the same normalization method used in Gabrilovich et al. (2009).

[DEPRECATED] * IndexPruner: prunes concept vectors for each term with a sliding window.
By default, window_size = 100 and threshold = 0.05 as in Gabrilovich et al. (2009). You can modify these values
in IndexPruner class.

* ESASearcher: performs search and computes vectors by using the resulting index in the database.

* TestESAVectors: produces and displays regular feature vector.

* TestGeneralESAVectors: produces and displays "Second Order Interpretation" vector filtered with "Concept Generality Filter" as in Gabrilovich et al. (2009).


DEPENDENCIES

Python scripts use MySQL-Python to access database.
MySQL-Python: http://sourceforge.net/projects/mysql-python/

Python scripts also use PyStemmer, which is the project encapsulating Python wrappers of Snowball:
You can find further info at: http://snowball.tartarus.org/download.php

"esa-lucene" Java project used for indexing, pruning etc. uses MySQL Connector/J to access database,
Lucene 3.0 for indexing and Trove and these libraries are included in project files.

MySQL Connector/J: http://www.mysql.com/downloads/connector/j/
Lucene 3.0: http://lucene.apache.org
Trove: http://trove4j.sourceforge.net/

pyre2 [optional] will speed up all regular expression parsing.
    hg clone https://re2.googlecode.com/hg/re2 re2.r56 && cd re2.r56 && hg update 56 && make -j4 && sudo make install
    easy_install re2
NOTE: re2 does not correctly handle Unicode (see
https://github.com/axiak/pyre2/issues/5). However, none of the regexes
use re.UNICODE, so I believe that its output will be identical.
WARNING: I should test re2 more. Sometimes the output is not what is
expected:
    https://github.com/axiak/pyre2/issues/5


USAGE

This creates the pagelinks table and records incoming and outgoing link counts.

python scanLinks.py <hgw.xml file from Wikiprep dump>

As stop categories, a list "wiki_stop_categories.txt" is provided.
But if you want to descend down and include all subtrees of these categories, you can use:

python scanCatHier.py <hgw.xml file from Wikiprep dump> <cat_hier output path>


[The commands below are standard]

python scanData.py <hgw.xml file from Wikiprep dump>
python addAnchors.py <anchor_text file from Wikiprep dump> <a writeable folder>

java -cp esa-lucene.jar edu.wiki.index.ESAWikipediaIndexer <Lucene index folder>

java -cp esa-lucene.jar edu.wiki.modify.IndexModifier <Lucene index folder>
... or, if you have a sufficient RAM (15 Gb was enough to process en-20090618 dump) try this instead:
java -cp esa-lucene.jar edu.wiki.modify.MemIndexModifier <Lucene index folder>

IndexModifier sorts TF-IDF vectors using sort utility of Unix, also using the disk.
MemIndexModifier handles sorting in memory instead.

Then perform a feature generation to test:

To generate regular features:
java -cp esa-lucene.jar edu.wiki.demo.TestESAVectors

To generate features using only more general links: 
java -cp esa-lucene.jar edu.wiki.demo.TestGeneralESAVectors
Something went wrong with that request. Please try again.