Triple
T19146375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Folklife Collection |
E468689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special collections library unit |
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: special collections library unit Context triple: [Southern Folklife Collection, instanceOf, special collections library unit]
-
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.
special edition collection
A special edition collection is a curated set of limited-release items distinguished by unique features, packaging, or content that differentiates them from standard versions.
-
E.
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.
- 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.