Philipp, Guido,

Guido would like to transform a sense lexicon "on the fly", making it a full-fledged axiomatized ontology just because it is mapped to an axiomatized ontology.
Now, we can obtain the same result with a two-step process, which I recommend usually when such problems arise with heterogeneous knowledge:

a) use a simple model to query (and modestly reason) over ontology+lexicon: with (a) most ontolex use cases will be satisfied, including Guido actually (ehm)
b) make a refactoring of the lexicon as an axiomatized ontology by using a "copycat" process: substitute senses to ontology entities (or make them equivalent to), and reason in regular DL mode

For (a), that's my attempt: I designed a simple OWL ontology (attached) for the example of Guido's, in a way that differs from both Guido's examples (can be considered an extension of example 1). It implements the basic pattern we are talking about (LexicalItem-hasSense->Sense-representedBy->OntologyEntity), augmented with a DomainEntity class and some properties between senses: specializes, and its subproperty meronymicallySpecializes. Now, instead of attempting any HODL reasoning, more modestly I show how to get a semantic field with a simple SPARQL query:

PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX owl: <http://www.w3.org/2002/07/owl#>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX ge: <http://www.ontologydesignpatterns.org/ont/guidoexample3.owl#>
CONSTRUCT { ?s1 ge:meronymicallySpecializes ?s }
 WHERE { 
  ?s ge:representedBy ge:Aircraft . 
  ?s1 ge:representedBy ?C1 .
  ?C1 rdfs:subClassOf ?R . 
  ?R owl:onProperty ge:partOf . 
  ?R ?quant ge:Aircraft }

Now the ball passes to Guido: when should we need (b), if your use case is satisfied already with (a)?

Ciao
Aldo