Triple
T24434893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of California Libraries system |
E616098
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research library consortium |
C343
|
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: research library consortium Context triple: [University of California Libraries system, instanceOf, research library consortium]
-
A.
research library
A research library is a specialized institution that collects, organizes, preserves, and provides access to scholarly resources and reference services to support advanced study and original research.
-
B.
academic library system
An academic library system manages the acquisition, organization, discovery, circulation, and preservation of scholarly resources to support the teaching, learning, and research needs of an academic institution.
-
C.
research infrastructure collection
A research infrastructure collection is an organized set of facilities, equipment, data, and services that together support and enable systematic scientific investigation and innovation.
-
D.
research consortium
chosen
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
-
E.
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.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:16 a.m.