Triple
T22497992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hospodar of Moldavia |
E556194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman vassal ruler |
C46395
|
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: Ottoman vassal ruler Context triple: [hospodar of Moldavia, instanceOf, Ottoman vassal ruler]
-
A.
Turkish beylik ruler
A Turkish beylik ruler is the sovereign leader of a small, often semi-independent principality (beylik) in medieval Anatolia, exercising military, political, and administrative authority over their territory and subjects.
-
B.
Karamanid ruler
A Karamanid ruler is the sovereign leader of the medieval Anatolian Turkish beylik of Karaman, responsible for governing its territories, directing military campaigns, and managing political and diplomatic relations with neighboring powers.
-
C.
Ottoman sultan
An Ottoman sultan is the supreme ruler of the Ottoman Empire, combining political, military, and religious authority as the head of state and caliph of the Muslim world.
-
D.
Aq Qoyunlu ruler
An Aq Qoyunlu ruler is a sovereign leader of the Aq Qoyunlu tribal confederation who exercised political, military, and administrative authority over its territories in Anatolia, Iran, and surrounding regions during the 14th–16th centuries.
-
E.
Seljuk sultan of Rum
A Seljuk sultan of Rum was the Muslim Turkic ruler of the Sultanate of Rum in Anatolia, governing a medieval state that emerged from the Great Seljuk Empire and served as a political and cultural bridge between the Islamic world and Byzantine-influenced Asia Minor.
- F. None of above. chosen
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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.