Triple
T23988920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GND |
E605010
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | integrated authority file |
C1034
|
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: integrated authority file Context triple: [GND, instanceOf, integrated authority file]
-
A.
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.
-
B.
international cooperative cataloging program
An international cooperative cataloging program is a collaborative initiative among libraries and related institutions worldwide to create, share, and maintain standardized bibliographic and authority records for more efficient and consistent resource discovery.
-
C.
authority control file
chosen
An authority control file is a structured database that standardizes names, subjects, and titles to ensure consistent identification and retrieval of entities across bibliographic and information systems.
-
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.
scholia
Scholia are marginal notes or explanatory comments, often by later scholars, that clarify, interpret, or critique a primary text.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:37 p.m.