Triple
T32300683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heraclias |
E825229
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine poetic work |
C60250
|
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 poetic work Context triple: [Heraclias, instanceOf, Byzantine poetic work]
-
A.
Byzantine poem
chosen
A Byzantine poem is a literary work composed in the Eastern Roman (Byzantine) Empire that blends classical Greek and Christian traditions, often written in learned Greek and characterized by intricate rhetoric, religious themes, and courtly or theological subject matter.
-
B.
Persian poetic work
A Persian poetic work is a literary composition written in the Persian language that employs verse, imagery, and traditional aesthetic forms to express themes such as love, mysticism, ethics, and philosophy.
-
C.
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.
-
D.
Byzantine philosophical work
A Byzantine philosophical work is a scholarly text produced in the Byzantine Empire that engages with classical Greek philosophy, Christian theology, and contemporary intellectual debates, often synthesizing them into a distinctively Orthodox worldview.
-
E.
Korean poetic work
A Korean poetic work is a literary composition written in the Korean language that uses rhythm, imagery, and traditional or modern poetic forms (such as sijo, gasa, or free verse) to express emotions, ideas, or narratives.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:45 a.m.