Triple
T31857712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanos of Constantinople |
E813241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Christian hymnographer |
C19641
|
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: Eastern Christian hymnographer Context triple: [Romanos of Constantinople, instanceOf, Eastern Christian hymnographer]
-
A.
Orthodox Christian hymnographic work
An Orthodox Christian hymnographic work is a liturgical or devotional text set to chant or song that poetically expresses and interprets the theology, feasts, saints, and spiritual life of the Orthodox Church.
-
B.
Syriac Christian poet
A Syriac Christian poet is a writer who composes religious and often liturgical verse in the Syriac language, blending biblical themes, theology, and local cultural motifs within the Syriac Christian tradition.
-
C.
Eastern Christian writer
chosen
An Eastern Christian writer is an author who produces theological, spiritual, or devotional works rooted in the traditions, doctrines, and cultural contexts of Eastern Christianity.
-
D.
Byzantine critic of hesychasm
A Byzantine critic of hesychasm is a theologian or intellectual from the Byzantine Empire who opposed or questioned the mystical, contemplative prayer practices and theological claims of hesychast monks, often on doctrinal, philosophical, or ecclesiastical grounds.
-
E.
Syriac Christian theologian
A Syriac Christian theologian is a scholar or religious thinker who develops, interprets, and systematizes Christian doctrine within the Syriac linguistic, liturgical, and cultural tradition.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:52 p.m.