Triple
T2101613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine poetry |
E37103
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine literature |
C2082
|
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 literature Context triple: [Byzantine poetry, instanceOf, Byzantine literature]
-
A.
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.
-
B.
ancient Greek literature
Ancient Greek literature encompasses the epic, lyric, dramatic, historical, and philosophical writings produced in the Greek language from the archaic through the Hellenistic periods, foundational to Western literary and intellectual traditions.
-
C.
Byzantine Greek
chosen
Byzantine Greek is the form of the Greek language used in the Eastern Roman (Byzantine) Empire from late antiquity to the fall of Constantinople, characterized by a mixture of classical, Koine, and emerging medieval features in grammar, vocabulary, and style.
-
D.
Byzantine law code
A Byzantine law code is a systematically organized collection of legal rules, imperial edicts, and judicial interpretations that governed civil, criminal, and ecclesiastical matters in the Byzantine Empire.
-
E.
Byzantine jurist
A Byzantine jurist is a legal scholar or judge of the Byzantine Empire who interpreted, applied, and commented on Roman and Byzantine law within the empire’s complex religious and imperial framework.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:43 p.m.