Triple

T7196419
Position Surface form Disambiguated ID Type / Status
Subject OWL 2 RL E168626 entity
Predicate basedOn P98 FINISHED
Object Web Ontology Language E4407 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: Web Ontology Language | Statement: [OWL 2 RL, basedOn, Web Ontology Language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Web Ontology Language
Context triple: [OWL 2 RL, basedOn, Web Ontology Language]
  • A. OWL 2 Web Ontology Language
    OWL 2 Web Ontology Language is a W3C-standardized knowledge representation language used to create, share, and reason over rich ontologies on the Semantic Web.
  • B. OWL DL
    OWL DL is a sublanguage of the Web Ontology Language that balances expressive power with computational decidability by adhering closely to description logic foundations.
  • C. OWL chosen
    OWL (Web Ontology Language) is a W3C-recommended semantic web language used to define and share rich, machine-interpretable ontologies on the web.
  • D. OWL 2 EL
    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.
  • E. 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.
  • 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_69c7bfa14e1c8190968b207bef0c96a9 completed March 28, 2026, 11:46 a.m.
Created at: March 27, 2026, 2:51 p.m.