Triple
T2186687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sack of Baghdad (1258) |
E49167
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongol invasion of the Middle East |
C7907
|
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: Mongol invasion of the Middle East Context triple: [Sack of Baghdad (1258), instanceOf, Mongol invasion of the Middle East]
-
A.
imperial war
Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
-
B.
Soviet–Finnish War
The Soviet–Finnish War, also known as the Winter War (1939–1940), was a conflict in which the Soviet Union invaded Finland to secure territory and strategic depth, facing unexpectedly strong Finnish resistance in harsh winter conditions.
-
C.
battle of the Spanish conquest of Peru
A battle of the Spanish conquest of Peru is a specific military engagement between Spanish conquistadors and Indigenous forces that occurred during the 16th-century campaign to subjugate and colonize the Inca Empire.
-
D.
Crusader state
A Crusader state is a feudal polity established by Western European crusaders in the Eastern Mediterranean and surrounding regions during the medieval Crusades, maintained through military, religious, and political control over conquered territories.
-
E.
European war
A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
- 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:45 p.m.