Triple
T7309085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | siege of Debal |
E168046
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Umayyad military campaign |
C20522
|
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: Umayyad military campaign Context triple: [siege of Debal, instanceOf, Umayyad military campaign]
-
A.
Islamic military campaign
chosen
An Islamic military campaign is an organized, often state-sanctioned, armed expedition undertaken by Muslim forces to expand, defend, or consolidate territories, influence, or religious-political objectives within an Islamic historical or ideological framework.
-
B.
Reconquista campaign
A Reconquista campaign is a coordinated military and political effort by Christian kingdoms in medieval Iberia to reclaim territories under Muslim rule, typically involving prolonged warfare, shifting alliances, and religiously framed objectives.
-
C.
papal military campaign
A papal military campaign is an organized armed expedition initiated, sanctioned, or led by the pope or the Papal States to pursue religious, political, or territorial objectives.
-
D.
Byzantine–Sasanian war
The Byzantine–Sasanian war is a prolonged series of military conflicts between the Eastern Roman (Byzantine) Empire and the Sasanian Persian Empire, marked by shifting frontiers, religious and political rivalry, and significant impacts on the balance of power in the Late Antique Near East.
-
E.
Mughal campaign
A Mughal campaign is a military expedition undertaken by the Mughal Empire to expand, consolidate, or defend its territories through organized warfare and strategic operations.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 3:01 p.m.