Triple

T31730241
Position Surface form Disambiguated ID Type / Status
Subject Romania (Byzantine Italy) E809840 entity
Predicate instanceOf P0 FINISHED
Object Byzantine territory C5854 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 territory
Context triple: [Romania (Byzantine Italy), instanceOf, Byzantine territory]
  • A. province of the Byzantine Empire chosen
    A province of the Byzantine Empire was an administrative and territorial unit governed by imperial officials, responsible for local civil, military, and fiscal management under the authority of the central Byzantine state.
  • B. Eastern Roman Empire
    The Eastern Roman Empire, also known as the Byzantine Empire, was the continuation of the Roman Empire in its eastern provinces, centered on Constantinople, that preserved Roman governance, law, and culture while developing a distinct Greek-speaking Christian civilization from late antiquity through the Middle Ages.
  • C. Byzantine client kingdom
    A Byzantine client kingdom was a semi-autonomous state that maintained its own local rulers and internal governance while recognizing the suzerainty of the Byzantine Empire, often providing military support, tribute, or political allegiance in exchange for protection and legitimacy.
  • D. 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.
  • E. Byzantine successor state
    A Byzantine successor state is a political entity that emerged from the fragmentation of the Byzantine Empire, claiming continuity with its imperial, cultural, and religious traditions.
  • 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_69f348e0e4908190a884582eca646fb7 completed April 30, 2026, 12:19 p.m.
Created at: April 30, 2026, 11:21 p.m.