Triple
T26083053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OWL 2 DL |
E657899
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Profile of OWL 2 |
C2887
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Profile of OWL 2 Context triple: [OWL 2 DL, instanceOf, Profile of OWL 2]
-
A.
Web ontology language
chosen
A web ontology language is a formal language designed for representing rich, machine-interpretable knowledge about concepts, relationships, and constraints on the web to enable automated reasoning and interoperability.
-
B.
Ontology-Based Data Access system
An Ontology-Based Data Access system is a framework that uses a formal ontology to provide a unified, semantic view over heterogeneous data sources, enabling users to query data at a conceptual level without needing to know the underlying schemas or storage details.
-
C.
ontology syntax
Ontology syntax is the formal set of rules and notations used to represent, structure, and interrelate concepts and relationships within an ontology in a machine- and human-readable way.
-
D.
SPARQL query engine
A SPARQL query engine is a software component that parses, optimizes, and executes SPARQL queries over RDF data sources to retrieve and manipulate semantic web data.
-
E.
RDF mapping language
An RDF mapping language is a formal language used to define how data from various sources is transformed and expressed as RDF triples, enabling semantic integration and interoperability across heterogeneous systems.
- F. None of above.
Provenance (1 batch)
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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:40 p.m.