Triple
T30804559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VIAF |
E784462
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | authority control service |
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 service Context triple: [VIAF, instanceOf, authority control service]
-
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.
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.
-
C.
library and information service
A library and information service is an organized system that collects, manages, and provides access to information resources and related assistance to meet the informational, educational, and recreational needs of its users.
-
D.
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.
-
E.
bibliographic service suite
A bibliographic service suite is an integrated set of tools and services that support the creation, management, discovery, and sharing of bibliographic records and related metadata across information 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:42 p.m.