Triple
T7616343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Business Library |
E172370
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic library branch |
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: academic library branch Context triple: [Business Library, instanceOf, academic library branch]
-
A.
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.
-
B.
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.
-
C.
school library
A school library is a dedicated learning space within an educational institution that provides students and staff with access to books, digital resources, and study areas to support reading, research, and academic growth.
-
D.
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.
-
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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:55 p.m.