Triple
T17521656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bioconductor |
E426691
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bioinformatics infrastructure |
C34934
|
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: bioinformatics infrastructure Context triple: [Bioconductor, instanceOf, bioinformatics infrastructure]
-
A.
bioinformatics program
A bioinformatics program is a software application designed to analyze, interpret, and manage biological data, such as DNA, RNA, and protein sequences, using computational and statistical methods.
-
B.
research infrastructure component
chosen
A research infrastructure component is a foundational hardware, software, or service element that supports the collection, storage, processing, and sharing of data and tools necessary for conducting and advancing research.
-
C.
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.
-
D.
computational analysis toolset
A computational analysis toolset is an integrated collection of software tools, libraries, and frameworks designed to process, analyze, and interpret data through algorithmic and statistical methods.
-
E.
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.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:49 a.m.