Triple
T9198204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISNI database |
E220768
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | authority control database |
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: authority control database Context triple: [ISNI database, instanceOf, authority control database]
-
A.
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.
-
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.
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.
-
E.
library control number
A library control number is a unique identifier assigned by a library or bibliographic agency to a specific catalog record, enabling precise tracking and retrieval of that item in library 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:25 p.m.