Triple
T18562351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerman Seljuk Sultanate |
E453676
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Seljuk dynasty branch |
C11026
|
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 dynasty branch Context triple: [Kerman Seljuk Sultanate, instanceOf, Seljuk dynasty branch]
-
A.
Muslim dynasty
chosen
A Muslim dynasty is a ruling family or lineage that governs a territory or state over successive generations under Islamic political, cultural, and religious principles.
-
B.
Mongol imperial dynasty branch
A Mongol imperial dynasty branch is a distinct ruling line or subdivision of the broader Mongol imperial family that governed a specific territory or khanate while sharing common ancestry and political heritage with the main Mongol Empire.
-
C.
Isma'ili dynasty
The Isma'ili dynasty refers to a series of Muslim ruling families and states historically led or influenced by Isma'ili Shi'a communities, most notably the Fatimid Caliphate, which combined religious leadership with political authority.
-
D.
Rurikid dynasty branch
A Rurikid dynasty branch is a lineage subgroup descending from the medieval Rurikid ruling family, typically associated with a specific territory, princely title, and period of political influence in Eastern Europe.
-
E.
member of the Ottoman dynasty
A member of the Ottoman dynasty is an individual belonging by birth or marriage to the ruling imperial family of the Ottoman Empire, historically entitled to varying degrees of political influence, privilege, and succession rights.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:42 a.m.