Triple

T28774726
Position Surface form Disambiguated ID Type / Status
Subject Δεσπότης Μυστρά E726502 entity
Predicate instanceOf P0 FINISHED
Object βυζαντινὸς ἄρχοντας C11929 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: βυζαντινὸς ἄρχοντας
Context triple: [Δεσπότης Μυστρά, instanceOf, βυζαντινὸς ἄρχοντας]
  • A. emperor of Nicaea
    The emperor of Nicaea was the sovereign ruler of the Empire of Nicaea, a Byzantine Greek successor state that preserved imperial authority and traditions following the Fourth Crusade’s capture of Constantinople.
  • B. emperor of Trebizond
    The emperor of Trebizond was the sovereign ruler of the Empire of Trebizond, a Byzantine successor state on the Black Sea coast, responsible for governing its territories, leading its military, and upholding its political and religious authority.
  • C. Eastern Roman emperor chosen
    An Eastern Roman emperor is the sovereign ruler of the eastern portion of the Roman Empire, later known as the Byzantine Empire, wielding supreme political, military, and religious authority.
  • D. regent of the Eastern Roman Empire
    A regent of the Eastern Roman Empire is an appointed or self-declared authority who governs the empire on behalf of a reigning but underage, absent, incapacitated, or otherwise unable emperor, wielding imperial power without holding the imperial title.
  • E. emperor of Thessalonica
    The emperor of Thessalonica was the sovereign ruler of the short-lived Byzantine successor state centered on the city of Thessalonica in the early 13th century, claiming imperial authority in competition with other Byzantine claimants.
  • 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_69f03199997c8190b6ae43fb19312443 completed April 28, 2026, 4:03 a.m.
Created at: April 28, 2026, 6:17 a.m.