Triple
T19690569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale University Library Digital Humanities Lab |
E472821
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital humanities lab |
C27772
|
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: digital humanities lab Context triple: [Yale University Library Digital Humanities Lab, instanceOf, digital humanities lab]
-
A.
digital humanities project
A digital humanities project is a scholarly initiative that uses computational tools and methods to analyze, interpret, and present humanities data in innovative, often interactive, digital forms.
-
B.
humanities laboratory
chosen
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.
digital humanities scholar
A digital humanities scholar is an academic who integrates computational tools and methods with humanistic inquiry to analyze, interpret, and present cultural, historical, and literary materials in new ways.
-
D.
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.
-
E.
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.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:45 p.m.