Triple
T2346755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberlin Group |
E45148
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic library consortium |
C9354
|
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 consortium Context triple: [Oberlin Group, instanceOf, academic library consortium]
-
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.
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.
-
C.
library and information science school
A library and information science school is an educational institution or academic unit that prepares students to manage, organize, preserve, and provide access to information resources across libraries, archives, and other information environments.
-
D.
consortium of colleges
chosen
A consortium of colleges is a collaborative association of independent higher education institutions that coordinate resources, programs, and services to enhance academic offerings and operational efficiency for their students and faculty.
-
E.
academic exchange organization
An academic exchange organization is an institution that facilitates and manages educational and cultural exchange programs between students, scholars, or institutions across different regions or countries.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:52 p.m.