Triple
T23988919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GND |
E605010
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | authority control system |
C1037
|
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 system Context triple: [GND, instanceOf, authority control system]
-
A.
authority control file
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.
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.
-
C.
bibliographic authority data set
chosen
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.
access control system
An access control system is a coordinated set of hardware, software, and policies that regulates and monitors who or what can enter, use, or interact with physical or digital resources based on defined permissions.
-
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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:37 p.m.