Triple
T23466752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bookshelf database |
E569119
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biomedical literature resource |
C36576
|
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: biomedical literature resource Context triple: [Bookshelf database, instanceOf, biomedical literature resource]
-
A.
library science literature
Library science literature encompasses scholarly and professional writings that examine the theories, practices, technologies, and management of libraries and information services.
-
B.
clinical search engine
A clinical search engine is a specialized information retrieval system that enables healthcare professionals to quickly find, filter, and interpret evidence-based medical information from clinical guidelines, research literature, and patient data.
-
C.
medical library
A medical library is a specialized information center that collects, organizes, and provides access to medical and health-related resources to support clinical practice, research, and education.
-
D.
bibliographic database provider
A bibliographic database provider is an organization or service that collects, curates, indexes, and delivers structured metadata about publications and scholarly works for search, discovery, and analysis.
-
E.
scientific compendium
chosen
A scientific compendium is a comprehensive, systematically organized collection of scientific knowledge, data, and references on a particular field or range of topics, intended to serve as an authoritative resource for study and research.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 5:54 p.m.