Triple
T1290225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BIBFRAME |
E27529
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bibliographic data model |
C6938
|
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 data model Context triple: [BIBFRAME, instanceOf, bibliographic data model]
-
A.
bibliographic data format
A bibliographic data format is a structured specification for representing, organizing, and exchanging information about published and unpublished resources such as books, articles, and other media.
-
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 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.
-
D.
bibliographic identifier
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.
-
E.
bibliographic project
A bibliographic project is an organized effort to collect, describe, and manage references to published or unpublished works around a specific topic, author, or field.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
Created at: March 1, 2026, 7:51 p.m.