Triple
T6519282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maschinelles Austauschformat für Bibliotheken |
E148340
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | machine-readable cataloging format |
C3555
|
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: machine-readable cataloging format Context triple: [Maschinelles Austauschformat für Bibliotheken, instanceOf, machine-readable cataloging format]
-
A.
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.
-
B.
cataloging record
A cataloging record is a structured set of metadata describing a resource (such as a book, media item, or digital object) to enable its identification, organization, and retrieval within a catalog or information system.
-
C.
bibliographic data format
chosen
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.
-
D.
library cataloging tool
A library cataloging tool is a system that helps librarians and users organize, classify, and retrieve library materials efficiently through standardized metadata and search functions.
-
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.
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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:44 p.m.