Triple
T25032891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langson Library |
E626897
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | humanities library |
C49716
|
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: humanities library Context triple: [Langson Library, instanceOf, humanities library]
-
A.
humanities department
A humanities department is an academic unit within an educational institution that focuses on the study, teaching, and research of disciplines exploring human culture, thought, history, and expression, such as literature, philosophy, history, languages, and the arts.
-
B.
humanities laboratory
A humanities laboratory is a collaborative, research-focused environment where scholars use experimental, digital, and interdisciplinary methods to investigate questions about human culture, history, and society.
-
C.
humanities research center
A humanities research center is an academic institution or organizational unit dedicated to advancing interdisciplinary study, collaboration, and public engagement in fields such as history, literature, philosophy, languages, and the arts.
-
D.
humanities research tool
A humanities research tool is a software system that supports scholars in collecting, organizing, analyzing, and interpreting humanistic data (such as texts, images, and artifacts) to facilitate critical inquiry and knowledge production.
-
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. chosen
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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:07 a.m.