Triple

T7196447
Position Surface form Disambiguated ID Type / Status
Subject OWL 2 RL E168626 entity
Predicate contrastedWith P278 FINISHED
Object OWL 2 EL E163073 NE FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: OWL 2 EL | Statement: [OWL 2 RL, contrastedWith, OWL 2 EL]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: OWL 2 EL
Context triple: [OWL 2 RL, contrastedWith, OWL 2 EL]
  • A. OWL 2 EL chosen
    OWL 2 EL is a lightweight profile of the Web Ontology Language designed for efficient reasoning over large-scale ontologies, particularly in domains like biomedical terminologies.
  • B. OWL 2 DL
    OWL 2 DL is a highly expressive yet decidable description logic–based profile of the OWL 2 Web Ontology Language, designed to balance rich modeling capabilities with computational completeness and decidability.
  • C. OWL 2 RL
    OWL 2 RL is a profile of the Web Ontology Language designed for scalable reasoning using rule-based systems, enabling efficient inference over large datasets.
  • D. OWL 2 Full
    OWL 2 Full is a highly expressive semantic web ontology language variant that fully integrates OWL with RDF, allowing powerful but undecidable reasoning over web data.
  • E. OWL 2 QL
    OWL 2 QL is a lightweight profile of the Web Ontology Language designed to enable efficient query answering over large datasets using standard relational database technologies.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69c68a5376748190bb500f03df86e93e completed March 27, 2026, 1:46 p.m.
NER Named-entity recognition batch_69c6e928ecdc8190a7f3feaf6d28781b completed March 27, 2026, 8:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69c802a38b608190bb87dd9af4fd3ef5 completed March 28, 2026, 4:32 p.m.
Created at: March 27, 2026, 2:51 p.m.