Triple
T29432476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hussein Dey |
E746471
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman 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 ruler Context triple: [Hussein Dey, instanceOf, Ottoman ruler]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Ottoman vassal ruler
chosen
An Ottoman vassal ruler was a semi-autonomous local sovereign who governed a territory under the suzerainty of the Ottoman Empire, owing tribute, military support, and political loyalty while retaining limited internal authority.
-
E.
Mamluk ruler
A Mamluk ruler is a sovereign who rose from a military slave background within the Mamluk system to wield political and military authority, often governing Islamic states such as medieval Egypt and Syria.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:14 p.m.