Research AI Landscape

DR-04-arts-humanities-tools

4 min read

DR-04 — AI Tools for Arts & Humanities Research

Purpose: Identify and profile AI tools serving Arts & Humanities researchers. This faculty grouping is nearly invisible in the current catalogue — only MAXQDA, NVivo, and Obsidian explicitly serve these researchers, and no tools for textual analysis, digital humanities, or archival/corpus research are catalogued.

Use with: Claude Research mode (or equivalent deep research tool)

Prompt

You are helping a UK research university (University of Sheffield) identify AI tools relevant to Arts & Humanities researchers. The university has strong departments in History, English Literature, Philosophy, Languages, Music, Architecture, and Cultural Studies. Profile the tools below, and identify any significant gaps in the list.

For each tool, research and return:

  1. Primary function — one sentence
  2. AI/ML features — specifically what AI capabilities are offered
  3. Disciplines served — which humanities/arts disciplines benefit most
  4. Licensing and cost — including any free tiers or academic pricing
  5. Data training policy — does user content train models?
  6. GDPR/data residency — EU/UK? DPA available?
  7. Accessibility — does the vendor publish an accessibility statement?
  8. HE adoption — named UK university deployments or Digital Humanities community usage
  9. Integration with existing tools — does it work with Zotero, Obsidian, Transkribus, EEBO, JSTOR, etc.?
  10. Catalogue status recommendation — adopt | trial | assess | hold

Sub-area A: Corpus and Text Analysis

  • Voyant Tools — web-based text analysis and visualisation (open source)
  • AntConc — corpus analysis toolkit (freeware, Laurence Anthony)
  • NLTK / spaCy with AI wrappers — Python NLP libraries increasingly used with LLM pipelines
  • GALC / Sketch Engine — corpus query system; widely used in linguistics
  • Stylo — R package for stylometric analysis (authorship attribution)
  • GATE (General Architecture for Text Engineering) — Sheffield-origin NLP framework
  • TXM — textometric platform (French-origin, widely used in DH)

Sub-area B: Handwritten Text Recognition & Archival AI

  • Transkribus (READ-COOP) — AI-powered HTR for historical manuscripts and documents
  • FromThePage — collaborative transcription platform with AI transcription
  • eScriptorium — open-source HTR platform (Kraken engine)
  • Document AI (Google) — cloud-based document understanding and OCR
  • Azure Document Intelligence (Microsoft) — AI form and document recognition

Sub-area C: Annotation and Semantic Linking

  • Recogito (Pelagios Network) — collaborative annotation linking text to places, people, and things
  • Hypothesis (web.hypothes.is) — open web annotation; widely used in humanities pedagogy and research
  • Catma — computer-assisted text markup and analysis (Hamburg)
  • INCEpTION — semantic annotation platform (TU Darmstadt)

Sub-area D: Digital Humanities Platforms

  • Omeka / Omeka S — open-source digital collections and exhibitions
  • Scalar (USC) — open-source authoring platform for born-digital scholarship
  • Nodegoat — network analysis and data management for humanities research
  • Palladio (Stanford) — humanities data visualisation
  • Gephi — network analysis and graph visualisation

Sub-area E: Audio, Image & Media Analysis for Humanities

  • ELAN — linguistic annotation of audio and video (Max Planck Institute)
  • Sonic Visualiser — audio analysis for musicology
  • Handprint — cloud AI image recognition for historical photographs
  • ImagePlot — large-scale image analysis and visualisation (culturomics)

Additional research questions

  1. LLM use in humanities: How are humanities researchers currently using general-purpose LLMs (ChatGPT, Claude, Gemini) for close reading, translation, archival research, and discourse analysis? What are the specific risks (hallucination, anachronism, bias) for humanities use cases?

  2. GATE at Sheffield: GATE (General Architecture for Text Engineering) was developed at the University of Sheffield. Is it still actively maintained? Does Sheffield IT Services provide any support for GATE? What is its current AI capability (v9+ neural pipelines)?

  3. AI and cultural heritage: Are there AI tools specifically designed for museum collections, cultural heritage documentation, or archive cataloguing that would be relevant to Sheffield’s humanities researchers?

  4. Digital humanities community: What tools does the ADHO (Alliance of Digital Humanities Organisations) and the DH community at UK universities recommend? Are there Jisc-supported digital humanities platforms?

Output format

For each sub-area, return a markdown table:

ToolFunctionAI featuresDisciplinesCostData trainingGDPRHE adoptionRecommended status

Follow with a priority list: top 3–5 tools the University of Sheffield should add to its AI catalogue immediately, with justification.

Note any tools where Sheffield has existing infrastructure, expertise, or origin (e.g. GATE).

Graph View