A toolkit for using self-hosted Natural Language Processing in WordPress
This plugin creates a custom Ingestor in your Elasticsearch cluster, prepared to process the post_content
from your posts using Open Source machine learning models created by the contributors to Apache OpenNLP. It also modifies your index mapping to account for the new entities extracted.
With the standard installation instructions, it will look for names of people and places, as well as dates, in any text processed, and save them to the Elasticsearch document representing your post. If the sync_to
filter in step 4 is used, the entities extracted are saved back to the WordPress database as taxonomy terms and/or post meta.
- It does not train any Machine Learning models using your data.
- It does not process your data in the webserver where WordPress is running.
This plugin is just a connector, Elasticsearch is doing all the heavy lifting.
- Elasticsearch 6.2.2+ running in a server you can install the models to
- ElasticPress 3.6+
- Follow the installation steps for the Elasticsearch OpenNLP Ingest Processor: install a processor version matching your Elasticsearch version, and don't forget to download the built-in modules. Do this in the server running Elasticsearch, not your webserver. e.g:
$ bin/elasticsearch-plugin install https://github.com/spinscale/elasticsearch-ingest-opennlp/releases/download/7.13.3.1/ingest-opennlp-7.13.3.1.zip
$ bin/ingest-opennlp/download-models
Configure elasticsearch.yml
to read the modules:
ingest.opennlp.model.file.persons: en-ner-persons.bin
ingest.opennlp.model.file.dates: en-ner-dates.bin
ingest.opennlp.model.file.locations: en-ner-locations.bin
- Make sure ElasticPress is active and a post index has been created.
- Install and activate this plugin.
- Add the following code to your
functions.php
to map the entities extracted to any existing taxonomies (optional):
add_filter( 'wnlptools_entity_copy_to', array( $this, 'wnlptools_copy_to' ), 10, 2 );
/**
* Example usage: maps any locations extracted using NLP to the Category taxonomy
*
* Extracted entities are saved in the `entities` key of the stored document in Elasticsearch
* so `entities.locations` contains all locations found in the document. However, this content
* only exists in Elasticsearch.
*
* With this method we are going to copy these locations to an existing taxonomy so they can be
* saved back to WordPress as categories.
*
* @param string $to current mapping, defaults to an empty string
* @param string $entity the entity mapped to $to
*
* @return string
*/
function wnlptools_sync_to( string $to, string $entity ) {
if ( 'locations' === $entity ) {
return 'terms.category';
}
if ( 'persons' === $entity ) {
return 'meta.persons';
}
if ( 'dates' === $entity ) {
return 'meta.dates';
}
return $to;
}
- The plugin only works with bulk indexing enabled.
- The ingester is only applied to the cluster upon activating the plugin. If it gets removed you need to deactivate and reactivate