Triple
T19146206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law Library at UNC-Chapel Hill |
E468685
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized academic library |
C15433
|
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: specialized academic library Context triple: [Law Library at UNC-Chapel Hill, instanceOf, specialized academic library]
-
A.
specialized branch library
chosen
A specialized branch library is a smaller, focused extension of a main library system that concentrates on a particular subject area, user group, or service type while providing targeted collections and expertise.
-
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 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.
-
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.
joint-use public and academic library
A joint-use public and academic library is a shared facility that simultaneously serves the general community and an educational institution’s students and staff, integrating collections, services, and spaces to meet both public and academic needs.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:06 p.m.