Triple
T5086325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongol invasion of Anatolia |
E114645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongol invasion |
C17523
|
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 Context triple: [Mongol invasion of Anatolia, instanceOf, Mongol invasion]
-
A.
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.
-
B.
Mongol invasion of Europe battle
A Mongol invasion of Europe battle is a military engagement in which Mongol forces confront European armies during their 13th-century westward campaigns, characterized by highly mobile cavalry tactics, psychological warfare, and often decisive Mongol victories.
-
C.
Turco-Mongol
Turco-Mongol refers to the historical synthesis of Turkic and Mongol political, military, and cultural traditions that shaped several Eurasian empires from the medieval to early modern periods.
-
D.
invasion of Russia
Invasion of Russia is a large-scale military campaign in which foreign forces attempt to penetrate, occupy, or subdue Russian territory, often facing vast distances, harsh climate, and strong defensive resistance.
-
E.
Viking raid
A Viking raid is a swift, seaborne assault by Norse warriors on coastal or riverside settlements, aimed at plunder, captives, and territorial influence.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:40 p.m.