Triple
T15336956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barakzai dynasty |
E366691
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pashtun dynasty |
C35943
|
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: Pashtun dynasty Context triple: [Barakzai dynasty, instanceOf, Pashtun dynasty]
-
A.
Persianate dynasty
A Persianate dynasty is a ruling family or political regime that, regardless of its ethnic origin, adopts and promotes Persian language, culture, administrative practices, and aesthetic ideals as the core framework of its governance and elite identity.
-
B.
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.
-
C.
Talpur dynasty ruler
A Talpur dynasty ruler is a sovereign from the Baluch Talpur clan who governed parts of Sindh in the late 18th and early 19th centuries, overseeing regional administration, military affairs, and cultural patronage until British annexation.
-
D.
Uzbek ruling house
The Uzbek ruling house is the dynastic lineage that held political authority and sovereignty over Uzbek territories, shaping the region’s governance, culture, and historical development.
-
E.
Armenian dynasty
An Armenian dynasty is a hereditary ruling family originating from Armenia that held political power and authority over Armenian territories during a specific historical period.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:17 a.m.