Triple
T24294591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medinan Muslim state |
E605923
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early Islamic polity |
C17263
|
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: early Islamic polity Context triple: [Medinan Muslim state, instanceOf, early Islamic polity]
-
A.
Early Muslim
An Early Muslim is an adherent of Islam from its formative centuries, whose beliefs, practices, and social life were shaped by the initial revelation to Muhammad and the subsequent development of the early Islamic community.
-
B.
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.
-
C.
Arabian polity
An Arabian polity is a political entity or state structure that governs a defined territory and population within the Arabian Peninsula or broader Arab world, shaped by regional history, culture, and power relations.
-
D.
Islamic polity
chosen
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.
-
E.
era of Islamic history
An era of Islamic history is a distinct period characterized by particular political structures, cultural developments, religious thought, and social dynamics within the broader historical trajectory of Muslim societies.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:09 a.m.