Triple
T19773797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge Structural Database |
E474953
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | crystallographic database |
C41251
|
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: crystallographic database Context triple: [Cambridge Structural Database, instanceOf, crystallographic database]
-
A.
crystallography journal
A crystallography journal is a periodical publication that presents peer-reviewed research, methods, and findings related to the determination and analysis of crystal structures and their properties.
-
B.
chemical database
chosen
A chemical database is a structured digital repository that stores, organizes, and enables retrieval of detailed information about chemical substances, their properties, reactions, and related data.
-
C.
commission of the International Union of Crystallography
A commission of the International Union of Crystallography is a specialized expert body established to advance, coordinate, and standardize research, methods, and communication within a particular subfield of crystallography worldwide.
-
D.
bibliographic database
A bibliographic database is a structured collection of references to published literature, such as books, articles, and reports, organized to support efficient search, retrieval, and management of bibliographic information.
-
E.
biological database
A biological database is an organized, searchable repository that stores, manages, and provides access to biological information such as sequences, structures, functions, and interactions of biomolecules and organisms.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:48 p.m.