Uploaded image for project: 'Stanbol'
  1. Stanbol
  2. STANBOL-723

Enhancement Engine for Disambiguation based on Solr MLT

    Details

    • Type: New Feature
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Enhancement Engines
    • Labels:

      Description

      This is an Enhancement Engine for Entity Disambiguation.

      Please do test it out. You can follow steps in Readme.

      Please provide your valuable feedback.

        Issue Links

          Activity

          Hide
          rwesten Rupert Westenthaler added a comment -

          no idea why this was marked as resolved. re-open to start progress.

          Show
          rwesten Rupert Westenthaler added a comment - no idea why this was marked as resolved. re-open to start progress.
          Hide
          rwesten Rupert Westenthaler added a comment -

          applied the patch with http://svn.apache.org/viewvc?rev=1378005&view=rev. Plan to finish initial code clean-up later today.

          Show
          rwesten Rupert Westenthaler added a comment - applied the patch with http://svn.apache.org/viewvc?rev=1378005&view=rev . Plan to finish initial code clean-up later today.
          Hide
          bdelacretaz Bertrand Delacretaz added a comment -

          See http://markmail.org/message/aubyruemy324o7ut for the current state and how to test this engine.

          Show
          bdelacretaz Bertrand Delacretaz added a comment - See http://markmail.org/message/aubyruemy324o7ut for the current state and how to test this engine.
          Hide
          jairost Jairo Sarabia added a comment -

          Hi all,

          I'm software developer at NotedLinks SL from Barcelona and here we're very interested in Apache Stanbol.
          We tried to install Disambiguation engine following the steps in http://markmail.org/message/aubyruemy324o7 but we haven't successfull.
          Ve got all the steps successfully except the last one:
          8. Try the disambiguation Engine at http://localhost:8080/enhancer/chain/dbpedia-keyword-disambiguation

          Then I tried to add Disambiguation engine (org.apache.stanbol.enhancer.engine.disambiguation.mlt-0.10.0-incubating-SNAPSHOT.jar) manually to "bundles" from Stanbol system console manager.
          this engine seems to activate correctly but when I try enhancer service it returns the error trace as follow:

          org.apache.stanbol.enhancer.servicesapi.ChainException: Enhancement Chain failed because of required Engine 'disambiguation-mlt' failed with Message: Unable to process ContentItem '<urn:content-item-sha1-e2ddeab70e1c93a5b55bb71986f3b27686e754d3>' with Enhancement Engine 'disambiguation-mlt' because the engine is currently not active(Reason: Unexpected Exception while processing ContentItem <urn:content-item-sha1-e2ddeab70e1c93a5b55bb71986f3b27686e754d3> with EnhancementJobManager: class org.apache.stanbol.enhancer.jobmanager.event.impl.EventJobManagerImpl)!
          at org.apache.stanbol.enhancer.jobmanager.event.impl.EventJobManagerImpl.enhanceContent(EventJobManagerImpl.java:153)
          at org.apache.stanbol.enhancer.jersey.resource.AbstractEnhancerResource.enhance(AbstractEnhancerResource.java:233)
          at org.apache.stanbol.enhancer.jersey.resource.AbstractEnhancerUiResource.enhanceFromForm(AbstractEnhancerUiResource.java:126)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          at java.lang.reflect.Method.invoke(Method.java:616)
          at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
          at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
          at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
          at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
          at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
          at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
          at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
          at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1483)
          at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1414)
          at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1363)
          at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1353)
          at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:414)
          at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
          at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:708)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
          at org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:96)
          at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:79)
          at org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42)
          at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49)
          at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
          at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:78)
          at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
          at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
          at org.apache.stanbol.commons.httpqueryheaders.impl.QueryHeadersFilter.doFilter(QueryHeadersFilter.java:75)
          at org.apache.felix.http.base.internal.handler.FilterHandler.doHandle(FilterHandler.java:88)
          at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:76)
          at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
          at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
          at org.apache.stanbol.commons.security.auth.AuthenticatingFilter$1.run(AuthenticatingFilter.java:159)
          at java.security.AccessController.doPrivileged(Native Method)
          at javax.security.auth.Subject.doAsPrivileged(Subject.java:537)
          at org.apache.stanbol.commons.security.auth.AuthenticatingFilter.doFilter(AuthenticatingFilter.java:155)
          at org.apache.felix.http.base.internal.handler.FilterHandler.doHandle(FilterHandler.java:88)
          at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:76)
          at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
          at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
          at org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48)
          at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39)
          at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:67)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
          at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
          at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
          at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
          at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
          at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
          at org.mortbay.jetty.Server.handle(Server.java:326)
          at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
          at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:943)
          at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
          at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
          at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
          at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
          at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
          Caused by: java.lang.IllegalStateException: Unexpected Exception while processing ContentItem <urn:content-item-sha1-e2ddeab70e1c93a5b55bb71986f3b27686e754d3> with EnhancementJobManager: class org.apache.stanbol.enhancer.jobmanager.event.impl.EventJobManagerImpl
          at org.apache.stanbol.enhancer.jobmanager.event.impl.EnhancementJobHandler.handleEvent(EnhancementJobHandler.java:187)
          at org.apache.felix.eventadmin.impl.tasks.HandlerTaskImpl.execute(HandlerTaskImpl.java:88)
          at org.apache.felix.eventadmin.impl.tasks.SyncDeliverTasks.execute(SyncDeliverTasks.java:221)
          at org.apache.felix.eventadmin.impl.tasks.AsyncDeliverTasks$TaskExecuter.run(AsyncDeliverTasks.java:110)
          at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
          at java.lang.Thread.run(Thread.java:679)
          Caused by: java.lang.NoSuchMethodError: org.apache.stanbol.enhancer.servicesapi.ContentItem.getMetadata()Lorg/apache/clerezza/rdf/core/access/LockableMGraph;
          at org.apache.stanbol.enhancer.engine.disambiguation.mlt.DisambiguatorEngine.computeEnhancements(DisambiguatorEngine.java:213)
          at org.apache.stanbol.enhancer.jobmanager.event.impl.EnhancementJobHandler.processEvent(EnhancementJobHandler.java:248)
          at org.apache.stanbol.enhancer.jobmanager.event.impl.EnhancementJobHandler.handleEvent(EnhancementJobHandler.java:181)
          ... 5 more

          Please could you help me?

          Thank you very much and congratulations for your great project!

          Show
          jairost Jairo Sarabia added a comment - Hi all, I'm software developer at NotedLinks SL from Barcelona and here we're very interested in Apache Stanbol. We tried to install Disambiguation engine following the steps in http://markmail.org/message/aubyruemy324o7 but we haven't successfull. Ve got all the steps successfully except the last one: 8. Try the disambiguation Engine at http://localhost:8080/enhancer/chain/dbpedia-keyword-disambiguation Then I tried to add Disambiguation engine (org.apache.stanbol.enhancer.engine.disambiguation.mlt-0.10.0-incubating-SNAPSHOT.jar) manually to "bundles" from Stanbol system console manager. this engine seems to activate correctly but when I try enhancer service it returns the error trace as follow: org.apache.stanbol.enhancer.servicesapi.ChainException: Enhancement Chain failed because of required Engine 'disambiguation-mlt' failed with Message: Unable to process ContentItem '<urn:content-item-sha1-e2ddeab70e1c93a5b55bb71986f3b27686e754d3>' with Enhancement Engine 'disambiguation-mlt' because the engine is currently not active(Reason: Unexpected Exception while processing ContentItem <urn:content-item-sha1-e2ddeab70e1c93a5b55bb71986f3b27686e754d3> with EnhancementJobManager: class org.apache.stanbol.enhancer.jobmanager.event.impl.EventJobManagerImpl)! at org.apache.stanbol.enhancer.jobmanager.event.impl.EventJobManagerImpl.enhanceContent(EventJobManagerImpl.java:153) at org.apache.stanbol.enhancer.jersey.resource.AbstractEnhancerResource.enhance(AbstractEnhancerResource.java:233) at org.apache.stanbol.enhancer.jersey.resource.AbstractEnhancerUiResource.enhanceFromForm(AbstractEnhancerUiResource.java:126) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288) at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1483) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1414) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1363) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1353) at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:414) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:708) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:96) at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:79) at org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42) at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49) at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33) at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:78) at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47) at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33) at org.apache.stanbol.commons.httpqueryheaders.impl.QueryHeadersFilter.doFilter(QueryHeadersFilter.java:75) at org.apache.felix.http.base.internal.handler.FilterHandler.doHandle(FilterHandler.java:88) at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:76) at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47) at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33) at org.apache.stanbol.commons.security.auth.AuthenticatingFilter$1.run(AuthenticatingFilter.java:159) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:537) at org.apache.stanbol.commons.security.auth.AuthenticatingFilter.doFilter(AuthenticatingFilter.java:155) at org.apache.felix.http.base.internal.handler.FilterHandler.doHandle(FilterHandler.java:88) at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:76) at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47) at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33) at org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48) at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39) at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:67) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:943) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) Caused by: java.lang.IllegalStateException: Unexpected Exception while processing ContentItem <urn:content-item-sha1-e2ddeab70e1c93a5b55bb71986f3b27686e754d3> with EnhancementJobManager: class org.apache.stanbol.enhancer.jobmanager.event.impl.EventJobManagerImpl at org.apache.stanbol.enhancer.jobmanager.event.impl.EnhancementJobHandler.handleEvent(EnhancementJobHandler.java:187) at org.apache.felix.eventadmin.impl.tasks.HandlerTaskImpl.execute(HandlerTaskImpl.java:88) at org.apache.felix.eventadmin.impl.tasks.SyncDeliverTasks.execute(SyncDeliverTasks.java:221) at org.apache.felix.eventadmin.impl.tasks.AsyncDeliverTasks$TaskExecuter.run(AsyncDeliverTasks.java:110) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Thread.java:679) Caused by: java.lang.NoSuchMethodError: org.apache.stanbol.enhancer.servicesapi.ContentItem.getMetadata()Lorg/apache/clerezza/rdf/core/access/LockableMGraph; at org.apache.stanbol.enhancer.engine.disambiguation.mlt.DisambiguatorEngine.computeEnhancements(DisambiguatorEngine.java:213) at org.apache.stanbol.enhancer.jobmanager.event.impl.EnhancementJobHandler.processEvent(EnhancementJobHandler.java:248) at org.apache.stanbol.enhancer.jobmanager.event.impl.EnhancementJobHandler.handleEvent(EnhancementJobHandler.java:181) ... 5 more Please could you help me? Thank you very much and congratulations for your great project!
          Hide
          rwesten Rupert Westenthaler added a comment -

          Hi

          > I'm software developer at NotedLinks SL from Barcelona and here we're very interested in Apache Stanbol.
          > We tried to install Disambiguation engine following the steps in http://markmail.org/message/aubyruemy324o7 but we haven't successfull.

          The link to the mail does not work for me, but I think I can remember its contents.

          The Error you see is due to a recent API change in the trunk that is not yet merged into the branch of the DisambiguationEngine. Updating the dependency of the Disambiguation Engine to the "org.apache.stanbol.enhancer.servicesapi" module should solve this. Simple search in the pom.xml file of the enigne for the dependency and adapt it to the following.

          <groupId>org.apache.stanbol</groupId>
          <artifactId>org.apache.stanbol.enhancer.servicesapi</artifactId>
          <version>0.10.0-SNAPSHOT</version>

          However you might still encounter problems because of mixing "-incubation-SNAPSHOT" of the branch with "-SNAPSHOT" bundles of the trunk within the same launcher. If this is the case you might need to wait until the POM changes of the trunk are merged into the branch.

          My current plan is to continue work on the disambiguation engine next week. Converting this branch so that is use the proper "-SNAPSHOT" dependencies will be the first thing to start with.

          best
          Rupert

          Show
          rwesten Rupert Westenthaler added a comment - Hi > I'm software developer at NotedLinks SL from Barcelona and here we're very interested in Apache Stanbol. > We tried to install Disambiguation engine following the steps in http://markmail.org/message/aubyruemy324o7 but we haven't successfull. The link to the mail does not work for me, but I think I can remember its contents. The Error you see is due to a recent API change in the trunk that is not yet merged into the branch of the DisambiguationEngine. Updating the dependency of the Disambiguation Engine to the "org.apache.stanbol.enhancer.servicesapi" module should solve this. Simple search in the pom.xml file of the enigne for the dependency and adapt it to the following. <groupId>org.apache.stanbol</groupId> <artifactId>org.apache.stanbol.enhancer.servicesapi</artifactId> <version>0.10.0-SNAPSHOT</version> However you might still encounter problems because of mixing "-incubation-SNAPSHOT" of the branch with "-SNAPSHOT" bundles of the trunk within the same launcher. If this is the case you might need to wait until the POM changes of the trunk are merged into the branch. My current plan is to continue work on the disambiguation engine next week. Converting this branch so that is use the proper "-SNAPSHOT" dependencies will be the first thing to start with. best Rupert
          Hide
          jairost Jairo Sarabia added a comment -

          Hello Rupert,

          Thanks for a quick response.

          I tried to change the pom.xml as you mention:

          <groupId> org.apache.stanbol </ groupId>
          <artifactId> org.apache.stanbol.enhancer.servicesapi </ artifactId>
          <version> 0.10.0-SNAPSHOT </ version>

          and I have compiled disambiguation Engine again, but now it seems that as you said, i have problems because of mixing "incubation-SNAPSHOT" with "SNAPSHOT". So i will be waiting until the POM changes of the trunk are merged into the branch.

          Also I was wondering, to test the results of disambiguation on a text, if it's possible you can send me a demo link with disambiguate Engine active. I would like to get an idea of the disambiguation results.

          Congratulations again. You are doing great project.

          Best

          Show
          jairost Jairo Sarabia added a comment - Hello Rupert, Thanks for a quick response. I tried to change the pom.xml as you mention: <groupId> org.apache.stanbol </ groupId> <artifactId> org.apache.stanbol.enhancer.servicesapi </ artifactId> <version> 0.10.0-SNAPSHOT </ version> and I have compiled disambiguation Engine again, but now it seems that as you said, i have problems because of mixing "incubation-SNAPSHOT" with "SNAPSHOT". So i will be waiting until the POM changes of the trunk are merged into the branch. Also I was wondering, to test the results of disambiguation on a text, if it's possible you can send me a demo link with disambiguate Engine active. I would like to get an idea of the disambiguation results. Congratulations again. You are doing great project. Best
          Hide
          rwesten Rupert Westenthaler added a comment -

          With the two commits [1] [2] from yesterday the disambiguation branch should once again be compatible with the Stanbol trunk. In addition it is now much easier to deploy the disambiguation engine on any Stanbol instance. Here are the required steps

          1. create a "fileinstall" directory within your

          {stanbol.home}

          folder (by default the stanbol home folder is "

          {stanbol-working-dir}

          /stanbol")
          2. copy the bundles of the disambiguation-ner engine [3], keyword linking engine [4] and the Enhancer jersey module [5] into the "fileinstall" directory.
          3. copy the configuration files for the dbpediakeyword KeywordLinkingEngine [6] and the keyworddisambiguation chain [7] to the "fileinstall" directory.

          Those files should be automatically recognized and installed to your stanbol instance. And you should be able to test the disambiguation-mlt engine by making requests to

          http://localhost:8080/enhancer/chain/dbpedia-keyword-disambiguation

          NOTES:

          • Following this instructions will replace the trunk versions of the Enhancer Jersey (RESTful API and Web UI) and KeywordLinking Engine with modified version of the disambiguation branch. While the Jersey only the UI was improved to better show disambiguation results there are some changes in the KeywordLinkingEngine that may affect results of other Enhancement Chains using this engine.
          • Step (2) can be replaced by any other way to install bundles to the OSGI environment such as using the "bundle" tab of the Felix Webconsole or the "mvn clean install -PinstallBundle -Dsling.url=http://localhost:8080/system/console" command ...
          • Step (3) can also be substituted by any other means to provide the required service configurations. However note that when configuring a KeywordLinkingEngine in a chain the uses the Disambiguation Engine it is important to increase the number of suggested entities (e.g. 10) and to apply more relaxed rules for suggesting Entities. Especially the "org.apache.stanbol.enhancer.engines.keywordextraction.minFoundTokens" should be set from the default two to one.

          best
          Rupert

          Related Commits:

          [1] http://svn.apache.org/viewvc?rev=1403904&view=rev
          [2] http://svn.apache.org/viewvc?rev=1403907&view=rev

          Bundles available after running "mvn clean install" on the disambiguation branch:

          [3]

          {disambiguation-trunk}/engines/disambiguation-mlt/target/org.apache.stanbol.enhancer.engine.disambiguation.mlt-0.10.0-SNAPSHOT.jar
          [4] {disambiguation-trunk}

          /engines/keywordextraction/target/org.apache.stanbol.enhancer.engine.keywordextraction-0.10.0-SNAPSHOT.jar
          [5]

          {disambiguation-trunk}

          /jersey/target/org.apache.stanbol.enhancer.jersey-0.10.0-SNAPSHOT.jar

          Configurations for a dbpedia disambiguation demo:

          [6] http://svn.apache.org/repos/asf/stanbol/branches/disambiguation-engine/defaults/src/main/resources/config/org.apache.stanbol.enhancer.engines.keywordextraction.engine.KeywordLinkingEngine-dbpediakeyword.config
          [7] http://svn.apache.org/repos/asf/stanbol/branches/disambiguation-engine/defaults/src/main/resources/config/org.apache.stanbol.enhancer.chain.weighted.impl.WeightedChain-keyworddisambiguation.config

          Show
          rwesten Rupert Westenthaler added a comment - With the two commits [1] [2] from yesterday the disambiguation branch should once again be compatible with the Stanbol trunk. In addition it is now much easier to deploy the disambiguation engine on any Stanbol instance. Here are the required steps 1. create a "fileinstall" directory within your {stanbol.home} folder (by default the stanbol home folder is " {stanbol-working-dir} /stanbol") 2. copy the bundles of the disambiguation-ner engine [3] , keyword linking engine [4] and the Enhancer jersey module [5] into the "fileinstall" directory. 3. copy the configuration files for the dbpediakeyword KeywordLinkingEngine [6] and the keyworddisambiguation chain [7] to the "fileinstall" directory. Those files should be automatically recognized and installed to your stanbol instance. And you should be able to test the disambiguation-mlt engine by making requests to http://localhost:8080/enhancer/chain/dbpedia-keyword-disambiguation NOTES: Following this instructions will replace the trunk versions of the Enhancer Jersey (RESTful API and Web UI) and KeywordLinking Engine with modified version of the disambiguation branch. While the Jersey only the UI was improved to better show disambiguation results there are some changes in the KeywordLinkingEngine that may affect results of other Enhancement Chains using this engine. Step (2) can be replaced by any other way to install bundles to the OSGI environment such as using the "bundle" tab of the Felix Webconsole or the "mvn clean install -PinstallBundle -Dsling.url= http://localhost:8080/system/console " command ... Step (3) can also be substituted by any other means to provide the required service configurations. However note that when configuring a KeywordLinkingEngine in a chain the uses the Disambiguation Engine it is important to increase the number of suggested entities (e.g. 10) and to apply more relaxed rules for suggesting Entities. Especially the "org.apache.stanbol.enhancer.engines.keywordextraction.minFoundTokens" should be set from the default two to one. best Rupert Related Commits: [1] http://svn.apache.org/viewvc?rev=1403904&view=rev [2] http://svn.apache.org/viewvc?rev=1403907&view=rev Bundles available after running "mvn clean install" on the disambiguation branch: [3] {disambiguation-trunk}/engines/disambiguation-mlt/target/org.apache.stanbol.enhancer.engine.disambiguation.mlt-0.10.0-SNAPSHOT.jar [4] {disambiguation-trunk} /engines/keywordextraction/target/org.apache.stanbol.enhancer.engine.keywordextraction-0.10.0-SNAPSHOT.jar [5] {disambiguation-trunk} /jersey/target/org.apache.stanbol.enhancer.jersey-0.10.0-SNAPSHOT.jar Configurations for a dbpedia disambiguation demo: [6] http://svn.apache.org/repos/asf/stanbol/branches/disambiguation-engine/defaults/src/main/resources/config/org.apache.stanbol.enhancer.engines.keywordextraction.engine.KeywordLinkingEngine-dbpediakeyword.config [7] http://svn.apache.org/repos/asf/stanbol/branches/disambiguation-engine/defaults/src/main/resources/config/org.apache.stanbol.enhancer.chain.weighted.impl.WeightedChain-keyworddisambiguation.config
          Hide
          rwesten Rupert Westenthaler added a comment -

          NOTE: The engine was merged into trunk (STANBOL-941). Please do not use the branch anymore.

          Show
          rwesten Rupert Westenthaler added a comment - NOTE: The engine was merged into trunk ( STANBOL-941 ). Please do not use the branch anymore.

            People

            • Assignee:
              rwesten Rupert Westenthaler
              Reporter:
              kritarth.anand Kritarth Anand
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:

                Development