Enhancement Engines
- org.apache.stanbol.enhancer.engines.opennlp.impl.NamedEntityExtractionEnhancementEngine
- org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine
You can enable, disable and deploy new engines using the
OSGi console.
Paste some text below and submit the form to let the active engines enhance it:
Stanbol is analysing your content...

Stateless REST analysis
This stateless interface allows the caller to submit content to the Stanbol enhancer engines and
get the resulting enhancements formatted as RDF at once without storing anything on the
server-side.
The content to analyze should be sent in a POST request with the mimetype specified in
the Content-type header. The response will hold the RDF enhancement serialized
in the format specified in the Accept header:
curl -X POST -H "Accept: text/turtle" -H "Content-type: text/plain" \
--data "John Smith was born in London." http://fise.demo.nuxeo.com/engines
The list of mimetypes accepted as inputs depends on the deployed engines. By default only
text/plain content will be analyzed
Stanbol enhancer is able to serialize the response in the following RDF formats:
application/json (JSON-LD)
application/rdf+xml (RDF/XML)
application/rdf+json (RDF/JSON)
text/turtle (Turtle)
text/rdf+nt (N-TRIPLES)
By default the URI of the content item being enhanced is a local, non
de-referencable URI automatically built out of a hash digest of the binary
content. Sometimes it might be helpful to provide the URI of the content-item
to be used in the enhancements RDF graph. This can be achieved by passing a
uri request parameter as follows:
curl -X POST -H "Accept: text/turtle" -H "Content-type: text/plain" \
--data "John Smith was born in London." \
"http://fise.demo.nuxeo.com/engines?uri=urn:fise-example-content-item"