Triple
T8203471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muslim conquest of Persia |
E191633
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 7th-century conflict |
C23661
|
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: 7th-century conflict Context triple: [Muslim conquest of Persia, instanceOf, 7th-century conflict]
-
A.
13th-century conflict
A 13th-century conflict is a military or political struggle that occurred between 1201 and 1300, shaped by medieval feudal structures, religious motivations, and emerging state powers.
-
B.
4th-century conflict
A 4th-century conflict is a historical dispute, war, or series of hostilities that occurred between 300 and 399 CE, shaped by the political, religious, and social dynamics of late antiquity.
-
C.
16th-century conflict
A 16th-century conflict is a historically documented military, political, or religious struggle that occurred between 1501 and 1600, involving organized groups or states and significantly influencing the social and geopolitical landscape of the early modern period.
-
D.
early 18th-century conflict
An early 18th-century conflict is a historically situated armed struggle or war occurring roughly between 1700 and 1750, shaped by emerging nation-states, dynastic rivalries, and evolving military technologies and tactics.
-
E.
war in the Middle Ages
War in the Middle Ages encompasses the organized, often feudal-based conflicts fought between kingdoms, nobles, and religious powers using evolving military technologies, tactics, and social structures from roughly the 5th to the 15th century.
- 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:43 p.m.