Triple
T15388514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kart dynasty |
E367975
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Islamic dynasty |
C15295
|
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: medieval Islamic dynasty Context triple: [Kart dynasty, instanceOf, medieval Islamic dynasty]
-
A.
Muslim dynasty
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.
Berber Muslim dynasty
A Berber Muslim dynasty is a ruling family or lineage of Berber origin that governed a region within the Islamic world, combining indigenous Amazigh (Berber) cultural elements with Islamic political and religious authority.
-
C.
Islamic empire
An Islamic empire is a large, multi-ethnic political entity historically governed by Muslim rulers who derive authority from Islamic law and tradition, integrating religious, cultural, and administrative systems across vast territories.
-
D.
Persianate dynasty
chosen
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.
-
E.
medieval Muslim principality
A medieval Muslim principality is a small, semi-independent political territory ruled by a Muslim prince or governor, typically owing nominal allegiance to a larger empire or caliphate while exercising local authority over military, legal, and economic affairs.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.