Triple
T25705364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harleian Library |
E644574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical library collection |
C25903
|
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: historical library collection Context triple: [Harleian Library, instanceOf, historical library collection]
-
A.
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.
-
B.
library collection
chosen
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.
historic library building
A historic library building is a culturally significant, often architecturally distinctive structure originally designed to house and provide public access to collections of books and other knowledge resources.
-
D.
humanities library
A humanities library is a specialized collection and space that curates, preserves, and provides access to resources focused on disciplines such as literature, history, philosophy, languages, and the arts to support research, teaching, and cultural inquiry.
-
E.
historical event collection
A historical event collection is an organized set of documented occurrences from the past, grouped and structured to support analysis, comparison, and retrieval based on time, place, theme, or significance.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 9:03 p.m.