Triple
T29208117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UniProt |
E740471
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protein information resource |
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 information resource Context triple: [UniProt, instanceOf, protein information resource]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
reference genome
A reference genome is a digital DNA sequence assembly that represents a typical example of a species’ genome, used as a standard framework for comparing and analyzing individual genetic variation.
-
E.
life sciences intelligence platform
A life sciences intelligence platform is a unified system that aggregates, analyzes, and visualizes scientific, clinical, and commercial data to support evidence-based decision-making across drug discovery, development, and commercialization.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 12:10 p.m.