Triple
T10350933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Architecture Library, University of Cambridge |
E243878
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university library unit |
C59
|
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: university library unit Context triple: [Architecture Library, University of Cambridge, instanceOf, university library unit]
-
A.
university administrative unit
A university administrative unit is an organizational division within a university responsible for managing specific operational, academic, or support functions to ensure the institution runs effectively and complies with policies and regulations.
-
B.
academic library system
chosen
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.
university museum service
A university museum service manages the curation, preservation, interpretation, and public presentation of collections to support the institution’s educational, research, and community engagement missions.
-
D.
undergraduate library
An undergraduate library is a campus facility that provides curated academic resources, study spaces, and research support services tailored to the needs of undergraduate students.
-
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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:57 a.m.