Triple
T767966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Digital Object Identifier system |
E16216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | persistent identifier system |
C1033
|
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: persistent identifier system Context triple: [Digital Object Identifier system, instanceOf, persistent identifier system]
-
A.
bibliographic identifier
chosen
A bibliographic identifier is a standardized code or string that uniquely distinguishes a specific published or unpublished bibliographic resource within catalogs, databases, or information systems.
-
B.
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.
-
C.
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.
-
D.
digital repository
A digital repository is a managed, long-term storage system that collects, preserves, and provides organized access to digital content and associated metadata.
-
E.
library cataloging standard
A library cataloging standard is a formal set of rules and guidelines that ensures consistent description, organization, and access to library materials across collections and systems.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.