Triple
T30462912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denkard |
E775059
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Middle Persian work |
C18628
|
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: Middle Persian work Context triple: [Denkard, instanceOf, Middle Persian work]
-
A.
Middle Persian text
chosen
A Middle Persian text is a written work composed in the Middle Iranian language of the Sasanian and early Islamic periods, typically preserved in Pahlavi script or related writing systems.
-
B.
Middle Persian name
A Middle Persian name is a personal or proper name originating from the Middle Persian language, used primarily in the Sasanian era and related historical contexts of the Iranian cultural sphere.
-
C.
Middle Persian language variety
A Middle Persian language variety is a historical form of the Persian language used roughly between the 3rd century BCE and the 9th century CE, characterized by its distinct phonology, morphology, and script traditions (such as Pahlavi) that differentiate it from Old and New Persian.
-
D.
Persianate Islamic text
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.
-
E.
Avestan text
An Avestan text is a written work composed in the Avestan language, primarily comprising the sacred scriptures and liturgical materials of Zoroastrianism.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:10 p.m.