Triple
T28483450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles F. Cummings New Jersey Information Center |
E720759
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | library special collection |
C15435
|
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: library special collection Context triple: [Charles F. Cummings New Jersey Information Center, instanceOf, library special collection]
-
A.
special collections department
chosen
The special collections department is a library unit responsible for acquiring, preserving, organizing, and providing controlled access to rare, unique, or fragile materials such as manuscripts, archives, rare books, and other distinctive resources.
-
B.
library collection
A library collection is an organized set of physical and/or digital information resources selected, acquired, and maintained by a library to support the informational, educational, and recreational needs of its users.
-
C.
specialized branch library
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.
-
D.
library catalogue
A library catalogue is an organized system that records and provides searchable access to a library’s collection of books, media, and other resources.
-
E.
historical library
A historical library is an institution that collects, preserves, and provides access to books, manuscripts, and other records of the past to support research, education, and cultural memory.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:56 a.m.