Triple
T15256890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sack of Opole |
E364669
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongol invasion event |
C13293
|
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 event Context triple: [Sack of Opole, instanceOf, Mongol invasion event]
-
A.
Mongol invasion
The Mongol invasion refers to the series of 13th- and 14th-century military campaigns by the Mongol Empire that rapidly expanded its control across Eurasia through highly mobile warfare, psychological tactics, and widespread destruction.
-
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.
Mongol conquest
The Mongol conquest refers to the series of 13th- and 14th-century military campaigns by the Mongol Empire that rapidly expanded its rule across Eurasia through highly mobile warfare, psychological tactics, and administrative integration of conquered peoples.
-
D.
Mongol invasion of Europe battle
chosen
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.
-
E.
Swedish invasion
A Swedish invasion is a large-scale military incursion initiated by Sweden into foreign territory, typically aimed at conquest, political influence, or strategic advantage.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:13 a.m.