Triple
T29107786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UniProtKB/Swiss-Prot |
E736813
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protein database |
C24488
|
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: protein database Context triple: [UniProtKB/Swiss-Prot, instanceOf, protein database]
-
A.
protein
A protein is a large, complex biological molecule composed of one or more chains of amino acids that fold into specific three-dimensional structures to perform diverse structural, catalytic, signaling, and regulatory functions in living organisms.
-
B.
biological database
chosen
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.
-
C.
biological database search system
A biological database search system is a software tool that enables users to efficiently query, retrieve, and analyze biological data (such as sequences, structures, and annotations) from one or more integrated databases.
-
D.
protein family
A protein family is a group of evolutionarily related proteins that share significant sequence, structural, and often functional similarity, indicating a common ancestral origin.
-
E.
Critical Assessment of protein Structure Prediction experiment
A Critical Assessment of Protein Structure Prediction experiment is a systematic, blind evaluation of computational methods for predicting protein 3D structures by comparing their predictions against experimentally determined reference structures.
- 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.