Triple
T14254423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NLM bibliographic services |
E353349
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bibliographic service suite |
C33658
|
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: bibliographic service suite Context triple: [NLM bibliographic services, instanceOf, bibliographic service suite]
-
A.
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.
-
B.
bibliographic database
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.
-
C.
bibliographic utility
A bibliographic utility is a tool or component that helps create, manage, format, and transform bibliographic data and citations across different standards and systems.
-
D.
bibliographic authority data set
A bibliographic authority data set is a structured collection of standardized records that uniquely identify and describe entities (such as persons, organizations, works, and subjects) used to control and link names and headings in bibliographic and library catalogs.
-
E.
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.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:09 a.m.