Triple
T16355028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Library Development |
E397154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | library development agency unit |
C21323
|
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: library development agency unit Context triple: [Division of Library Development, instanceOf, library development agency unit]
-
A.
library standards office
The library standards office is a specialized unit responsible for developing, maintaining, and enforcing policies, procedures, and quality standards that govern library operations, services, and collections.
-
B.
development authority
A development authority is an organization or governmental body responsible for planning, regulating, and facilitating land use, infrastructure, and urban or regional development within a designated area.
-
C.
library and information service
chosen
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 district
A library district is a defined geographic area governed by a dedicated public entity that funds, manages, and provides library services to the residents within its boundaries.
-
E.
organizational unit of the Library of Congress
An organizational unit of the Library of Congress is a distinct administrative division, such as a department, office, or service, responsible for specific functions that support the Library’s overall mission and operations.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.