Triple
T35045325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo the Deacon’s History |
E1011180
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine historical narrative |
C18376
|
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 historical narrative Context triple: [Leo the Deacon’s History, instanceOf, Byzantine historical narrative]
-
A.
Byzantine chronicle
chosen
A Byzantine chronicle is a historical narrative, often arranged annalistically, that records events of the Byzantine Empire and surrounding regions, typically blending factual reporting with religious interpretation and classical traditions.
-
B.
Byzantine history event
A Byzantine history event is a significant occurrence within the Eastern Roman (Byzantine) Empire that influenced its political, religious, military, social, or cultural development.
-
C.
Latin narrative history
Latin narrative history is a genre of historical writing in Latin that presents past events in a continuous, story-like prose, often emphasizing character, causation, and moral or political interpretation.
-
D.
Byzantine encyclopedia
A Byzantine encyclopedia is a comprehensive medieval reference work compiled in the Byzantine Empire, systematically organizing knowledge on theology, history, literature, science, and daily life according to contemporary scholarly and religious perspectives.
-
E.
Byzantine theme
A Byzantine theme was a military-administrative district of the Byzantine Empire, governed by a strategos who oversaw both civil administration and regional defense.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.