Triple
T28399651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biosafety Clearing-House |
E719367
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biosafety information system |
C54006
|
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: biosafety information system Context triple: [Biosafety Clearing-House, instanceOf, biosafety information system]
-
A.
biosafety protocol
A biosafety protocol is a structured set of procedures and guidelines designed to prevent exposure to and release of biological agents, ensuring the safety of personnel, the public, and the environment.
-
B.
NIH information system
An NIH information system is an integrated digital platform that manages, stores, and facilitates secure access to biomedical research data, administrative records, and operational information across the National Institutes of Health.
-
C.
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.
-
D.
biobank
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.
-
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. chosen
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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:19 a.m.