Triple
T9669887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kassia |
E233998
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine composer |
C19516
|
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: Byzantine composer Context triple: [Kassia, instanceOf, Byzantine composer]
-
A.
Georgian composer
A Georgian composer is a musician from the country of Georgia who creates original musical works, often blending traditional Georgian musical elements with broader classical or contemporary styles.
-
B.
post-Byzantine painter
A post-Byzantine painter is an artist working in the Eastern Christian world after the fall of Constantinople who continued and adapted Byzantine iconographic and stylistic traditions under changing cultural, political, and religious influences.
-
C.
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.
-
D.
Byzantine scholar
A Byzantine scholar is a learned individual specializing in the language, theology, history, and culture of the Byzantine Empire, often engaging in the preservation, interpretation, and commentary of classical and Christian texts.
-
E.
Byzantine person
chosen
A Byzantine person is an individual who lived in or was culturally associated with the Byzantine Empire, characterized by its Eastern Roman heritage, Orthodox Christian faith, and rich traditions in art, law, and administration.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:15 p.m.