Triple
T3758939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Library of Congress Linked Data Service |
E82115
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | linked data service |
C5633
|
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: linked data service Context triple: [Library of Congress Linked Data Service, instanceOf, linked data service]
-
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.
open data index
An open data index is a systematic ranking or assessment framework that evaluates and compares the availability, accessibility, quality, and usability of open government or institutional data across different entities or jurisdictions.
-
C.
bibliographic data model
A bibliographic data model is a structured framework that defines how information about published and unpublished resources (such as books, articles, and digital media) is represented, organized, and related for purposes of description, discovery, and management.
-
D.
indexing service
chosen
An indexing service is a system component that scans, organizes, and maintains searchable references to data or documents to enable fast and efficient retrieval.
-
E.
link invariant
A link invariant is a quantity or property assigned to a link (a collection of intertwined loops in three-dimensional space) that remains unchanged under ambient isotopies, distinguishing links up to continuous deformation.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:35 p.m.