Triple
T29107174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PDBx/mmCIF dictionary |
E736791
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ontology for macromolecular structure data |
C6250
|
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 for macromolecular structure data Context triple: [PDBx/mmCIF dictionary, instanceOf, ontology for macromolecular structure data]
-
A.
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.
-
B.
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.
-
C.
ontology
chosen
An ontology is a structured conceptual model that defines the entities, relationships, and rules within a specific domain to enable shared understanding and reasoning.
-
D.
Crystallographic Information Framework extension
A Crystallographic Information Framework extension is a standardized, machine-readable schema that augments the core CIF dictionary with additional data items and definitions to support specialized crystallographic or related scientific domains.
-
E.
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.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 11:16 a.m.