Triple
T20649324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nure Sufi Bey |
E507444
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | founder of a beylik |
C1844
|
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: founder of a beylik Context triple: [Nure Sufi Bey, instanceOf, founder of a beylik]
-
A.
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.
-
B.
Turkic bey
A Turkic bey is a tribal or regional chieftain who held military, administrative, and political authority within Turkic societies, often serving as a vassal or subordinate ruler under a greater sovereign.
-
C.
founder of dynasty
chosen
A founder of dynasty is the original leader who establishes a ruling family line, initiating its political, social, and cultural legacy.
-
D.
Zengid ruler
A Zengid ruler is a sovereign or governor from the Zengid dynasty, a 12th–13th century Muslim Turkic ruling house that controlled parts of Syria and northern Iraq, known for its military campaigns against Crusader states and efforts to unify Muslim territories.
-
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.
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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:43 a.m.