Triple
T31802254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zubayrid regime |
E811772
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical Islamic polity |
C24030
|
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: historical Islamic polity Context triple: [Zubayrid regime, instanceOf, historical Islamic polity]
-
A.
Islamic polity
An Islamic polity is a political entity whose governance, legal framework, and public life are formally grounded in Islamic principles, law (Sharia), and moral values, as interpreted by its ruling authorities and religious scholars.
-
B.
historical polities
chosen
Historical polities are organized political entities or governing structures that existed in the past, such as kingdoms, empires, city-states, and federations, defined by their territorial control, institutions, and sociopolitical systems.
-
C.
Islamic historical entity
An Islamic historical entity is any person, group, institution, event, or polity significantly associated with the development, practice, or influence of Islam across history.
-
D.
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.
-
E.
Islamic historical concept
An Islamic historical concept is an idea, practice, institution, or event rooted in the development of Muslim societies over time, shaped by Islamic beliefs, law, culture, and interactions with other civilizations.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:42 p.m.