Triple
T3439937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umayyad conquest of Hispania |
E72540
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Islamic conquest |
C7960
|
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: Islamic conquest Context triple: [Umayyad conquest of Hispania, instanceOf, Islamic conquest]
-
A.
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.
-
B.
Mongol invasion of the Middle East
The Mongol invasion of the Middle East was a series of 13th- and 14th-century military campaigns by the Mongol Empire that devastated major Islamic centers, reshaped regional political structures, and facilitated new patterns of trade and cultural exchange across Eurasia.
-
C.
Islamization
chosen
Islamization is the historical and social process by which individuals, communities, or regions adopt Islamic beliefs, practices, and cultural norms, often transforming existing religious and societal structures.
-
D.
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.
-
E.
turning point in Islamic history
A turning point in Islamic history is a pivotal event or period that significantly alters the religious, political, social, or cultural trajectory of Muslim societies and reshapes the development of the Islamic world.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:16 p.m.