Triple
T656834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Library of Congress authority record |
E11666
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | authority record |
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 record Context triple: [Library of Congress authority record, instanceOf, authority record]
-
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.
legal record
A legal record is an official document or collection of documents that formally captures, preserves, and provides evidence of legal actions, decisions, rights, and obligations.
-
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.
acquisition authority
Acquisition authority is the legally granted power or permission for an individual or organization to obtain, purchase, or otherwise secure goods, services, or assets on behalf of an entity.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:36 p.m.