Triple
T26099264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jami al-Tawarikh manuscripts |
E658351
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Persian manuscript |
C22096
|
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: Persian manuscript Context triple: [Jami al-Tawarikh manuscripts, instanceOf, Persian manuscript]
-
A.
Quran manuscript
A Quran manuscript is a handwritten copy of the Islamic holy book, often richly decorated and produced with meticulous care to preserve and transmit the sacred text.
-
B.
Persianate Islamic text
chosen
A Persianate Islamic text is a written work produced within the cultural sphere shaped by Persian language, literary norms, and aesthetics that engages with Islamic religious, philosophical, legal, or mystical themes.
-
C.
Insular manuscript
An Insular manuscript is a handwritten book produced in the British Isles between the 7th and 9th centuries, characterized by distinctive Hiberno-Saxon script, intricate interlace ornament, and elaborate decorated initials.
-
D.
Glagolitic manuscript
A Glagolitic manuscript is a handwritten document produced using the Glagolitic alphabet, one of the earliest Slavic scripts, typically preserving religious, liturgical, or legal texts from the medieval Slavic cultural sphere.
-
E.
Hungarian manuscript
A Hungarian manuscript is a handwritten document originating from Hungary, typically composed in Hungarian or Latin, that reflects the historical, literary, legal, or religious culture of the region in a given period.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:53 p.m.