Triple
T938872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Northern War |
E20259
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early modern 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: early modern war Context triple: [Great Northern War, instanceOf, early modern war]
-
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.
early modern state
An early modern state is a centralized political entity that emerged in Europe between the 15th and 18th centuries, characterized by growing bureaucratic administration, territorial sovereignty, standing armies, and increasingly standardized systems of law and taxation.
-
C.
early modern polity
An early modern polity is a territorially bounded, politically organized community between roughly 1500 and 1800 that exercised authority through evolving institutions of governance, law, and sovereignty amid processes of state formation and imperial expansion.
-
D.
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.
-
E.
military history
Military history is the study of armed conflict across time, examining wars, battles, strategies, technologies, and their political, social, and cultural impacts on societies.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:40 p.m.