Triple
T19146422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University Archives (UNC-Chapel Hill) |
E468690
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special collections 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 unit Context triple: [University Archives (UNC-Chapel Hill), instanceOf, special collections 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.
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.
-
C.
specialist museum
A specialist museum is a cultural institution dedicated to collecting, preserving, researching, and exhibiting artifacts and information focused on a specific subject, discipline, or theme.
-
D.
cultural heritage object collection
A cultural heritage object collection is an organized assemblage of artifacts, artworks, or historical items preserved and managed to represent and transmit the cultural, historical, or artistic legacy of a community or society.
-
E.
specialist unit
A specialist unit is a dedicated organizational subgroup composed of experts and specialized resources focused on performing specific, complex, or high-priority tasks within a broader system or institution.
- 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.