Triple
T27523125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of the Book collections |
E694764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized research collection |
C51619
|
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: specialized research collection Context triple: [History of the Book collections, instanceOf, specialized research collection]
-
A.
research infrastructure collection
A research infrastructure collection is an organized set of facilities, equipment, data, and services that together support and enable systematic scientific investigation and innovation.
-
B.
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.
-
C.
special collections department
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.
-
D.
academic collection
chosen
An academic collection is an organized set of scholarly works, such as articles, books, datasets, or other research materials, curated around a specific discipline, topic, or purpose for study and reference.
-
E.
specialized laboratory
A specialized laboratory is a facility equipped with focused instruments, technologies, and expertise dedicated to conducting advanced research, testing, or analysis within a specific scientific or technical domain.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:22 p.m.