Triple
T16560308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalal al-Din Karatay |
E402319
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Seljuk official |
C37630
|
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: Seljuk official Context triple: [Jalal al-Din Karatay, instanceOf, Seljuk official]
-
A.
Timurid official
A Timurid official was an administrative or military functionary serving the Timurid Empire, responsible for implementing imperial policies, managing provincial governance, and maintaining order and revenue collection under the authority of the Timurid rulers.
-
B.
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.
-
C.
Abbasid official
An Abbasid official was a bureaucrat or administrator serving the Abbasid Caliphate, responsible for managing state affairs such as taxation, justice, military logistics, and provincial governance within the empire’s centralized administrative system.
-
D.
Khan of Bukhara
The Khan of Bukhara is the sovereign ruler of the Khanate of Bukhara, a Central Asian polity historically centered in the city of Bukhara and exercising political, military, and religious authority over its territories.
-
E.
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.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:15 a.m.