Triple
T26894626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shah Beg Arghun |
E677866
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arghun dynasty ruler |
C52177
|
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: Arghun dynasty ruler Context triple: [Shah Beg Arghun, instanceOf, Arghun dynasty ruler]
-
A.
Timurid ruler
A Timurid ruler is a sovereign from the Timurid dynasty (14th–16th centuries) who governed territories in Central Asia, Iran, and surrounding regions, often noted for military conquest, Persianate court culture, and patronage of arts and architecture.
-
B.
Manghit dynasty ruler
A Manghit dynasty ruler is a sovereign from the Uzbek Manghit family who governed the Emirate of Bukhara, overseeing its political, military, and religious affairs from the mid-18th to early 20th centuries.
-
C.
Ashtarkhanid dynasty ruler
An Ashtarkhanid dynasty ruler is a sovereign from the Uzbek-origin Ashtarkhanid (Janid) line who governed the Khanate of Bukhara in Central Asia between the late 16th and mid-18th centuries.
-
D.
Afsharid ruler
An Afsharid ruler is a sovereign belonging to the Afsharid dynasty that governed Iran and surrounding regions in the 18th century, exercising political, military, and administrative authority over its territories.
-
E.
Sayyid dynasty ruler
A Sayyid dynasty ruler is a sovereign from the Sayyid lineage who governed parts of northern India during the early 15th century, claiming descent from the Prophet Muhammad and ruling primarily from Delhi.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:47 a.m.