Triple
T22722954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hannover Unified Biobank |
E561913
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | centralized biomedical research biobank |
C12203
|
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: centralized biomedical research biobank Context triple: [Hannover Unified Biobank, instanceOf, centralized biomedical research biobank]
-
A.
biobank
chosen
A biobank is an organized repository that collects, processes, stores, and manages biological samples and associated data for use in research, diagnostics, and therapeutic development.
-
B.
bioscience research center
A bioscience research center is a specialized facility where scientists conduct experimental and computational studies on living systems to advance knowledge and develop applications in health, agriculture, and biotechnology.
-
C.
computational biology research center
A computational biology research center is an institution that develops and applies computational, statistical, and mathematical methods to analyze biological data and address complex problems in life sciences and medicine.
-
D.
translational research center
A translational research center is an institution that integrates basic scientific discoveries with clinical and community applications to accelerate the development, testing, and implementation of new diagnostics, therapies, and health interventions.
-
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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:20 p.m.