Triple
T22363966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMC Calendars of manuscripts |
E552852
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | calendar of manuscripts |
C34400
|
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: calendar of manuscripts Context triple: [HMC Calendars of manuscripts, instanceOf, calendar of manuscripts]
-
A.
manuscript catalogue
chosen
A manuscript catalogue is a systematically organized listing that describes and indexes individual manuscripts within a collection, typically including details such as authorship, date, provenance, physical characteristics, and content summaries.
-
B.
manuscript collection
A manuscript collection is an organized group of handwritten, typed, or otherwise unpublished documents, often related by creator, subject, or provenance, preserved and managed as a single archival unit.
-
C.
ancient manuscripts
Ancient manuscripts are original handwritten documents from past civilizations, typically preserved on materials like papyrus, parchment, or early paper, that provide primary evidence of historical, religious, literary, or scientific thought.
-
D.
manuscript museum
A manuscript museum is an institution dedicated to collecting, preserving, studying, and exhibiting historical and culturally significant handwritten documents and texts.
-
E.
late antique manuscript
A late antique manuscript is a handwritten document produced between roughly the 3rd and 8th centuries CE, typically on papyrus or parchment, reflecting the transitional cultural, religious, and artistic practices of the late Roman and early medieval worlds.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:44 p.m.