Triple
T1530495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PubMed Central |
E32429
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biomedical literature database |
C1031
|
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 database Context triple: [PubMed Central, instanceOf, biomedical literature database]
-
A.
bibliographic database
chosen
A bibliographic database is a structured collection of references to published literature, such as books, articles, and reports, organized to support efficient search, retrieval, and management of bibliographic information.
-
B.
scientific manuscript collection
A scientific manuscript collection is an organized repository of research papers and related scholarly documents, curated for preservation, access, and systematic study.
-
C.
bibliographic data model
A bibliographic data model is a structured framework that defines how information about published and unpublished resources (such as books, articles, and digital media) is represented, organized, and related for purposes of description, discovery, and management.
-
D.
research library
A research library is a specialized institution that collects, organizes, preserves, and provides access to scholarly resources and reference services to support advanced study and original research.
-
E.
biodiversity database
A biodiversity database is a structured digital repository that stores, organizes, and provides access to data on species, their distributions, traits, and ecological relationships to support research, conservation, and environmental management.
- 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_69a885ea86308190998f6bc14bb91f8e |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:26 p.m.