Triple
T38378974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdullah Khan Uzbek |
E893704
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Shaybanid dynasty member |
C63668
|
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: Shaybanid dynasty member Context triple: [Abdullah Khan Uzbek, instanceOf, Shaybanid dynasty member]
-
A.
Shaybanid ruler
chosen
A Shaybanid ruler is a sovereign from the Shaybanid dynasty, a branch of the Uzbek tribes who governed large parts of Central Asia—especially Transoxiana and Khwarezm—from the early 16th to the late 16th century.
-
B.
Salian dynasty member
A Salian dynasty member is an individual belonging to the German royal and imperial family that ruled the Holy Roman Empire from 1024 to 1125, originating from the Frankish nobility along the Rhine.
-
C.
member of the Karrani dynasty
A member of the Karrani dynasty is an individual belonging to the Afghan-origin ruling family that controlled the Bengal Sultanate in the late 16th century, known for being the last independent sultans of Bengal before Mughal annexation.
-
D.
member of the Durrani dynasty
A member of the Durrani dynasty is an individual belonging to the Pashtun royal lineage that ruled Afghanistan and parts of surrounding regions from the mid-18th to the 19th century, originating with Ahmad Shah Durrani.
-
E.
Borjigin dynasty member
A Borjigin dynasty member is an individual belonging to the royal clan descended from Genghis Khan that ruled and influenced Mongol and related polities across Eurasia.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.