Triple
T11844366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taifa of Murcia |
E281734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Muslim principality |
C30486
|
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 Muslim principality Context triple: [Taifa of Murcia, instanceOf, medieval Muslim principality]
-
A.
Turkish principality
A Turkish principality is a semi-independent, territorially defined political entity ruled by a Turkish dynastic leader, typically emerging in the medieval or early modern period within the broader context of Turkic state formation and regional power dynamics.
-
B.
Armenian principality
An Armenian principality is a semi-autonomous political entity historically governed by Armenian nobility, exercising regional authority under varying degrees of dependence on larger empires or kingdoms.
-
C.
medieval Iranian state
A medieval Iranian state is a historically situated political entity in the Iranian plateau and surrounding regions, characterized by dynastic rule, Persianate administrative and cultural traditions, and interaction with neighboring Islamic and Eurasian powers between roughly the 7th and 15th centuries.
-
D.
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.
-
E.
Sultanate
A Sultanate is a form of monarchy or state ruled by a sultan, typically characterized by Islamic governance traditions and varying degrees of centralized authority.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:43 p.m.