Triple

T1862729
Position Surface form Disambiguated ID Type / Status
Subject Third Silesian War E34852 entity
Predicate instanceOf P0 FINISHED
Object Silesian War C472 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: Silesian War
Context triple: [Third Silesian War, instanceOf, Silesian War]
  • A. battle of the Franco-Dutch War
    A battle of the Franco-Dutch War is a military engagement fought between 1672 and 1678 involving France and its allies against the Dutch Republic and its shifting coalition of European powers, typically characterized by complex political motives and evolving alliances.
  • 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. European war chosen
    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.
  • D. succession war
    A succession war is an armed conflict triggered by competing claims to a throne or leadership position, typically following the death, deposition, or disputed legitimacy of a ruler.
  • E. 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.
  • 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_69a88600b2f88190bc09303e68ab517e completed March 4, 2026, 7:20 p.m.
Created at: March 4, 2026, 7:34 p.m.