Triple
T31803632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court of Leo I |
E811809
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine court |
C57138
|
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 court Context triple: [court of Leo I, instanceOf, Byzantine court]
-
A.
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.
-
B.
Byzantine regency
Byzantine regency refers to the temporary governance arrangement in the Byzantine Empire whereby one or more regents exercised imperial authority on behalf of an underage, absent, or incapacitated emperor.
-
C.
Byzantine imperial palace
A Byzantine imperial palace is a grand, fortified residential and ceremonial complex that housed the emperor and court, combining administrative, religious, and domestic functions in richly decorated architectural spaces.
-
D.
Byzantine institution
chosen
A Byzantine institution is a formal organization or structure within the Byzantine Empire—such as its imperial bureaucracy, church hierarchy, legal system, or military administration—defined by complex procedures, centralized authority, and a fusion of Roman, Christian, and local traditions.
-
E.
Byzantine imperial dynasty
A Byzantine imperial dynasty is a succession of related rulers who governed the Eastern Roman (Byzantine) Empire, shaping its political, religious, and cultural life over multiple generations.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:42 p.m.