<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Leveraging Meta-Modelling Language for Ontology Structuring and Validation</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Zekeri Adams</string-name>
          <email>zekeri.adams@fmph.uniba.sk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Martin Homola</string-name>
          <email>homola@fmph.uniba.sk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ján Kľuka</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Vojtěch Svátek</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Comenius University Bratislava</institution>
          ,
          <addr-line>Mlynská dolina, 842 48 Bratislava</addr-line>
          ,
          <country country="SK">Slovakia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Prague University of Business and Economics</institution>
          ,
          <addr-line>Nám. W. Churchilla 1938/4, 130 67 Praha 3</addr-line>
          ,
          <country country="CZ">Czech Republic</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Knowledge representation (KR) is foundational to AI, providing the structures that enable systems to reason and interpret complex domains, powering applications like expert systems and intelligent agents. Yet, traditional KR methods struggle with the growing complexity in fields like biomedicine, finance, and cybersecurity, where interdependencies and rapid change challenge accurate representation. Meta-modeling ofers a flexible solution with reusable frameworks that improve adaptability. Ontological meta-modeling, in particular, provides hierarchical structures for more abstract, adaptable models. However, current frameworks often lack standardized formal structures and strong theoretical foundations, limiting practical adoption. Issues in validation and consistency further constrain scalability in real-world settings. Our research addresses these gaps by formalizing the PURO meta-modeling language, focusing on theoretical rigor and verification techniques for consistency. We also present use cases in Wikidata to showcase enhanced expressiveness and reliability in representing complex, dynamic knowledge domains.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Meta-modeling</kwd>
        <kwd>ontology</kwd>
        <kwd>PURO</kwd>
        <kwd>MLT</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Meta-modeling is a methodology that represents the structure and relationships of models at a higher
level of abstraction, enabling the creation of frameworks applicable across various domains. In ontologies,
it provides an abstract schema that defines the rules and relationships governing elements, ensuring a
standardized and reusable approach to modeling knowledge. This is essential for structuring complex
domains efectively [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ] . It defines how classes, properties, and individuals interact within a domain,
specifying relationships and constraints to maintain consistency, scalability, and adaptability. This is
particularly important in fields where entity relationships are constantly evolving [
        <xref ref-type="bibr" rid="ref3 ref4">3, 4</xref>
        ].
      </p>
      <p>
        A key benefit of meta-modeling is its ability to enhance ontology coherence. By introducing
welldefined meta-level schemas, it avoids redundancy and conflicting definitions, ensuring a coherent
representation of knowledge. It also systematically defines class interrelations, such as inheritance
and composition, reflecting real-world structures more accurately [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. This coherence is critical for
maintaining the reliability of the represented knowledge.
      </p>
      <p>
        Although numerous meta-modeling languages have been proposed, many lack a formal logical
foundation. One work in this direction is the multi-level modelling theory, MLT [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. This theory
addresses the modeling of domains that involve multiple classification levels. It is designed to formally
characterize the nature of these classification levels and define the structural relationships both within
entities of the same level and between entities at diferent levels. MLT is grounded in the concepts of types
and individuals. In the theory, types are viewed as predicative entities (e.g., "Person", "Organization",
"Product") that can apply to multiple entities, including other types. When a type  applies to an entity
, we say that  is an instance of . Conversely, individuals are entities that cannot have instances,
such as “John”, “an apple”, or “my cellphone”. MLT also accounts for the stratification of types into
various orders, such as individual, first-order types, second-order types, and so on. This framework is
axiomatized in first-order logic, where both individuals and types are quantified, forming the entities in
the theory. A fundamental aspect of MLT is the instance of relation, which connects entities to the
types they instantiate [
        <xref ref-type="bibr" rid="ref6 ref7">7, 6</xref>
        ].
      </p>
      <p>
        Fonseca et.al. [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], applied the theory to the well-known knowledge base, Wikidata, which structures
items using RDF (subject-predicate-object) format. Wikidata’s item hierarchy is inherently multi-leveled,
utilizing the instance of (P31) and subclass of (P279) relations to stratify items into diferent classification
levels. The classification of items in Wikidata includes individual entities, fixed-order classes, and
variable-order classes, classes with orders ranging from the first to higher levels. However, the study
[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] revealed that despite this classification system, multi-level anti-patterns (they involve classification
of entities as individuals or classes of some order conflicting with instantiation and specialization
relationships among them) persist. These multi-level anti-patterns underscoring the challenges of
maintaining a coherent multi-level classification system. Although, Fonseca et.al. [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], identified
antipatterns in Wikidata, they were unable to provide a visualization of these patterns beyond the syntactic
errors revealed by the logical axioms. Additionally, there was no validation of the logical axioms or the
detected syntactic errors within Wikidata.
      </p>
      <p>
        Our study focuses on the meta-modeling language PURO [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], and its formalization in first-order
logic. PURO provides a robust framework for structuring and understanding ontologies, combining
logical formalization with a graphical tool, the PURO Modeler, for ontology visualization. In this work,
we validate the satisfiability of the PURO formalization using the widely recognized theorem prover,
Vampire [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Furthermore, we explore the practical application of the language with its graphical tool
within Wikidata, a prominent knowledge base, to analyze and identify potential structural issues and
the validation of its structure.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. PURO Language</title>
      <p>
        PURO [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] is a graphical language designed to simplify the creation of OWL ontologies [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] and OntoUML
models [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. It provides a foundational set of modeling elements, such as objects and their associated
types, relationships, and quantitatively valued attributes. One of the distinctive features of PURO is
its support for multi-level types, allowing for the hierarchical organization of types across diferent
abstraction levels, which enhances the expressiveness of ontological models. Additionally, PURO
supports relations of arbitrary arity, enabling the modeling of more complex relationships between
entities that involve multiple participants.
      </p>
      <p>
        Ontologies developed using the PURO language are constructed through the PURO Modeler [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], a
web graphical tool that facilitates the visualization and structuring of ontological elements. The PURO
Modeler allows users to interactively build and manipulate ontologies, with the primitives shown in
Figure 1. This visual approach not only enhances the user experience but also ensures that the logical
structure of the ontology remains clear and accessible, making it easier to model complex domains.
      </p>
      <p>A PURO ontological background model establishes two fundamental distinctions: one between
ontological particulars and universals, and another between objects, relationships, and valuations.
These distinctions result in the creation of six basic PURO terms. They include:
• B-object represents specific objects, often real-world entities, which can be tangible (like people,
animals, or objects) or intangible (such as concepts, events, or processes). This concept parallels
the notion of individuals in traditional models.
• B-type represents a universal entity whose instances are entities belonging to the same concept
or sharing a common property. B-types generalize the concept of classes and cover qualities (e.g.,
red color), although there may be slight ontological diferences. B-types are multilevel (that is,
B-type 1, B-type 2, B-type 3, and so on).</p>
      <p>• B-relationship denotes a specific relationship between two or more entities, such as a musical
work being composed by a composer, or an object being produced by a producer. It also includes
relationships like an object being of a certain type or one type of goods being a special case of
another.
• B-relation refers to a conceptual relation, serving as the universal counterpart of B-relationship.</p>
      <p>It resembles the more restricted ontological notion of an object property, with instances of
B-relations being B-relationships.
• B-valuation involves the assignment of a quantitative data value to an entity, typically a
Bobject. Unlike B-relationships, B-valuations are always binary, with their second participants
being quantitative data values. This aligns with the notion of data property assertion in regular
ontologies.
• B-attribute represents a universal consisting of valuations of the same quantitative property. They
are akin to the regular notion of data properties and attributes in ER schemas.</p>
      <p>These primitives serve as the foundational predicates in the formalization of the PURO language
within first-order logic. Also, the binary predicate instanceOf is employed to signify that a particular
entity belongs to the extension of a universal, and the infix binary predicate : (colon) associates an
entity with a PURO term by (1a).</p>
      <p>:  → Entity() ∧ PuroTerm()
instanceOf(, ) → Entity() ∧ Entity()
∃ (instanceOf(, ) →  : Universal)
(1a)
(1b)
(1c)
Axiom (1b) specifies that the instanceOf property is used to establish a relationship between two entities.
Axiom (1c) further clarifies that an entity  is considered an instance of an entity  that is associated
with a Universal—meaning  can be a B-type, B-relation, or B-attribute. By using the instanceOf
property, we create a clear and formal structure for representing hierarchical relationships within
the ontology, ensuring that each entity is accurately classified according to its designated type. An
important consequence of Axioms (1b) and (1c) is that particulars do not themselves have instances,
reinforcing a structured hierarchy where instances relate only to Universals and not to other particulars:
 : Particular → ¬∃ instanceOf(, )
(2)</p>
    </sec>
    <sec id="sec-3">
      <title>3. Formal verification of PURO axiomatization and use case</title>
      <p>A central objective of our research is the exploration of PURO axiomatization, which has proven
efective in supporting ontology development and structuring. Validating this framework is crucial to
ensure both its logical consistency and the satisfiability of the models built upon it. Logical consistency
ensures that the models are free from contradictions, while satisfiability guarantees that the models can
be interpreted without violating any imposed constraints.</p>
      <p>
        To facilitate this validation, we encoded the PURO axiomatization using the TPTP syntax [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. For
example, we encode (1a), (1b) and (1c) in TPTP syntax, below:
fof(colon_sorts, axiom, ![X,T]: (colon(X, Y) =&gt; (entity(X) &amp; puroterm(T)))).
fof(instof_sorts, axiom, ![X,Y]: (instanceof(X, Y) =&gt; (entity(X) &amp; entity(Y)))).
fof(has_instance_universal, axiom,
      </p>
      <p>![Y]: (?[X]: instanceof(X, Y) =&gt; colon(Y, universal))).</p>
      <p>We then used the first-order logic theorem prover Vampire to verify the satisfiability of PURO’s
axiomatization. The result obtained was satisfiable, validating the correctness of the axiomatization.</p>
      <p>We apply the PURO modeler to real-world examples and validated their satisfiability using Vampire.
Each tested example proved to be satisfiable, highlighting the robustness of the PURO framework in
real-world ontology development. This validation supports the use of PURO for building ontologies
that can handle intricate relationships while remaining logically sound.</p>
      <p>To further assess the practical applicability of our approach, we extended our investigation to
Wikidata, a large-scale collaborative knowledge base. Using SPARQL queries, we identified structural
inconsistencies in Wikidata, highlighted in Figure 2, where the PURO modeler points out specific errors.
The SPARQL Query shown below targets entities ? and ?, both acting as instances of the first-order
class Q104086571 (directly or through specializations) with ? instantiating ?.</p>
      <p>PREFIX wd: &lt;http://www.wikidata.org/entity/&gt;
PREFIX wdt: &lt;http://www.wikidata.org/prop/direct/&gt;
SELECT DISTINCT ?x ?y WHERE {
?x wdt:P31/(wdt:P279*) wd:Q104086571.
?y wdt:P31/(wdt:P279*) wd:Q104086571.</p>
      <p>?x wdt:P31/(wdt:P279*) ?y.</p>
      <p>}
A similar SPARQL query was executed for the second-order class Q24017414 in place of Q104086571,
and in both cases, a significant number of inconsistencies were identified.</p>
      <p>Two examples of the identified inconsistencies are depicted in Figure 2. On the left side of the figure,
the entity iPhone 15 Pro (Q12244399), which is categorized as a first-order class, is marked as an instance
of Cell phone model (Q19723444). However, Cell phone model (Q19723444), itself an instance of Type of
manufactured goods (Q22811462), is classified as a second-order class (B-type 2). This violates constraint
(3a), as Type of manufactured goods (Q22811462) is designated as a second-order class (B-type 2) in
Wikidata, creating a conflict.</p>
      <p>On the right side of Figure 2, the entity Hypotrichosis (Q1641483), a subclass of Hair disease (Q2989168),
is incorrectly shown as an instance of Rare disease (Q929833). This contradicts constraint (3b), as Rare
disease (Q929833) is categorized as a B-type 1 class, leading to further inconsistency.
¬∃( : B-type1 ∧  : B-type2)
¬∃( : B-type2 ∧  : B-type3)
∀,  (instanceOf(, ) ∧  : B-type2 →  : B-type1)
∀,  (instanceOf(, ) ∧  : B-type3 →  : B-type2)
(3a)
(3b)
(3c)
(3d)
This analysis revealed the challenges of maintaining coherence in large, evolving datasets and
highlighted the importance of using formal tools like PURO modeler to detect and address these issues,
ensuring more reliable and consistent data structures.</p>
      <p>We also extended our formal verification to the models depicted in Figure 2. The model on the
left of Figure 2 was encoded using PURO axioms, as shown in (4a) and (4b) in TPTP syntax, and
tested in Vampire. This resulted in a refutation, indicating inconsistencies or unsatisfiability within its
logical structure. Similarly, the model on the right of Figure 2 was encoded using PURO axioms, also
transformed into TPTP syntax. The same result, a refutation, was obtained, confirming the presence of
inconsistencies.</p>
      <p>Q12244399 : B-type1 ∧ Q19723444 : B-type2 ∧ instanceOf(Q12244399, Q19723444)
Q19723444 : B-type2 ∧ Q22811462 : B-type2 ∧ instanceOf(Q19723444, Q22811462)
(4a)
(4b)
These refutations reinforce the critical role of thorough logical analysis in ontology modeling, as even
well-designed models can reveal hidden flaws when subjected to rigorous testing.</p>
      <p>The inconsistencies identified in these models suggest areas that require further refinement, such as
the item Type of manufactured goods (Q22811462) should be properly categorized as a third-order class
(B-type 3) and the item Rare disease (Q929833) should be properly categorized as a second-order class
(B-type 2). This is necessary to achieve logical soundness.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Conclusion</title>
      <p>Our work highlights the crucial role of the PURO Modeler in structuring and visualizing ontologies,
enhancing the clarity and organization of complex models. By ofering a clear framework for
understanding hierarchical relationships, the PURO Modeler improves the efectiveness of ontology design.
Additionally, we emphasize the importance of formal verification tools like Vampire in detecting and
resolving logical inconsistencies, ensuring the integrity of ontologies built with the PURO language.</p>
      <p>Our experiments with PURO, which revealed some incoherences in Wikidata, stress the need for
rigorous logical validation in knowledge representation. Addressing these issues enhances both the
reliability and efectiveness of ontologies, making them better suited for applications in AI, knowledge
management, and semantic web technologies.</p>
      <p>The combination of PURO’s flexible structure and Vampire’s verification power provides a scalable
and robust foundation for building consistent ontologies that can adapt to evolving domains. This
synergy ensures that ontology-driven technologies remain reliable as they grow to support increasingly
complex applications of knowledge representation.</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgments</title>
      <p>This work was supported by the Slovak Republic under SRDA grants nos. APVV-23-0292 (DyMAX) and
APVV-20-0353 (APEColT). Vojtěch Svátek has been partially supported by the EU’s Horizon Europe
grant no. 101058682 (Onto-DESIDE).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>A.</given-names>
            <surname>Gangemi</surname>
          </string-name>
          ,
          <article-title>Ontology design patterns for semantic web content</article-title>
          ,
          <source>in: Proceedings of the International Semantic Web Conference (ISWC)</source>
          ,
          <year>2005</year>
          , pp.
          <fpage>262</fpage>
          -
          <lpage>276</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>N.</given-names>
            <surname>Guarino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Oberle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          ,
          <article-title>What is an ontology?</article-title>
          , in: Handbook on Ontologies, Springer,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>N. F.</given-names>
            <surname>Noy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. L.</given-names>
            <surname>McGuinness</surname>
          </string-name>
          ,
          <article-title>Ontology Development 101: A Guide to Creating Your First Ontology</article-title>
          ,
          <source>Technical Report, Stanford Knowledge Systems Laboratory</source>
          ,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Studer</surname>
          </string-name>
          , Handbook on Ontologies, Springer,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>J.</given-names>
            <surname>Euzenat</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Shvaiko</surname>
          </string-name>
          , Ontology Matching, Springer,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>C. M.</given-names>
            <surname>Fonseca</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. P.</given-names>
            <surname>Almeida</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Guizzardi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V. A.</given-names>
            <surname>Almeida</surname>
          </string-name>
          <article-title>, Multi-level conceptual modeling: Theory, language</article-title>
          , and application,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>V.</given-names>
            <surname>Almeida</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. P.</given-names>
            <surname>Almeida</surname>
          </string-name>
          ,
          <article-title>Toward a well-founded theory for multi-level conceptual modeling (</article-title>
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>V.</given-names>
            <surname>Svátek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Homola</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Kľuka</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Vacura</surname>
          </string-name>
          ,
          <article-title>Mapping structural design patterns in OWL to ontological background models</article-title>
          ,
          <source>in: Proceedings of the Seventh International Conference on Knowledge Capture (K-CAP '13)</source>
          , ACM, New York, NY, USA,
          <year>2013</year>
          , pp.
          <fpage>117</fpage>
          -
          <lpage>120</lpage>
          . doi:
          <volume>10</volume>
          .1145/ 2479832.2479847.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>L.</given-names>
            <surname>Kovács</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Voronkov</surname>
          </string-name>
          ,
          <article-title>First-order theorem proving and vampire</article-title>
          , in: N.
          <string-name>
            <surname>Sharygina</surname>
          </string-name>
          , H. Veith (Eds.),
          <source>Computer Aided Verification - 25th International Conference, CAV</source>
          <year>2013</year>
          ,
          <string-name>
            <given-names>Saint</given-names>
            <surname>Petersburg</surname>
          </string-name>
          , Russia,
          <source>July 13-19</source>
          ,
          <year>2013</year>
          . Proceedings, volume
          <volume>8044</volume>
          of Lecture Notes in Computer Science, Springer,
          <year>2013</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>35</lpage>
          . URL: https://doi.org/10.1007/978-3-
          <fpage>642</fpage>
          -39799-
          <issue>8</issue>
          _
          <fpage>1</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>M.</given-names>
            <surname>Dudáš</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Svátek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Vacura</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Zamazal</surname>
          </string-name>
          ,
          <article-title>Starting ontology development by visually modeling an example situation - a user study</article-title>
          ,
          <source>in: VOILA@ISWC</source>
          , volume
          <volume>1704</volume>
          <source>of CEUR Workshop Proceedings, CEUR-WS.org</source>
          ,
          <year>2016</year>
          , pp.
          <fpage>114</fpage>
          -
          <lpage>119</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>M.</given-names>
            <surname>Dudáš</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Morkus</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Svátek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T. P.</given-names>
            <surname>Sales</surname>
          </string-name>
          , G. Guizzardi,
          <article-title>Kickstarting ontouml modeling from PURO instance-level examples</article-title>
          ,
          <source>in: Procs. EKAW 2020 Posters and Demonstrations Session</source>
          , volume
          <volume>2751</volume>
          <source>of CEUR Workshop Proceedings, CEUR-WS.org</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>36</fpage>
          -
          <lpage>40</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>G.</given-names>
            <surname>Sutclife</surname>
          </string-name>
          ,
          <article-title>The TPTP Problem Library and Associated Infrastructure. From CNF to TH0</article-title>
          ,
          <source>TPTP v6.4.0, Journal of Automated Reasoning</source>
          <volume>59</volume>
          (
          <year>2017</year>
          )
          <fpage>483</fpage>
          -
          <lpage>502</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>