Triple
T34498885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court of Theodosius I |
E885693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late Roman imperial institution |
C6483
|
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: late Roman imperial institution Context triple: [court of Theodosius I, instanceOf, late Roman imperial institution]
-
A.
Roman imperial household
The Roman imperial household comprised the emperor’s family, slaves, freedmen, and administrative staff who managed both the private affairs and many public functions of the imperial court.
-
B.
Byzantine institution
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.
-
C.
Roman Republican institution
A Roman Republican institution is a political, legal, or social structure that operated within the Roman Republic’s mixed constitution to distribute authority, regulate civic life, and balance power among magistrates, assemblies, and the Senate.
-
D.
imperial institution
chosen
An imperial institution is a formal organization or structure established by an empire to administer, control, and legitimize its authority over territories and populations.
-
E.
Roman imperial dynasty
A Roman imperial dynasty is a succession of emperors from the same family or household who ruled the Roman Empire over a continuous period, sharing political power, legitimacy, and often common policies or agendas.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.