Triple
T7115486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OBDA systems |
E165807
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ontology-based data access technology |
C7267
|
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: ontology-based data access technology Context triple: [OBDA systems, instanceOf, ontology-based data access technology]
-
A.
Web ontology language
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.
bibliographic data model
A bibliographic data model is a structured framework that defines how information about published and unpublished resources (such as books, articles, and digital media) is represented, organized, and related for purposes of description, discovery, and management.
-
C.
knowledge representation framework
chosen
A knowledge representation framework is a structured system of formalisms, models, and conventions used to encode, organize, and manipulate information so that it can be interpreted and reasoned about by humans and machines.
-
D.
open knowledge organization
An open knowledge organization is a collaborative, transparent system for structuring, connecting, and sharing information that allows broad participation in creating, maintaining, and reusing knowledge resources.
-
E.
database theory conference
A database theory conference is a formal academic gathering where researchers present and discuss advances in the theoretical foundations of data management, querying, and database 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:43 p.m.