Triple
T2694582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schmalkaldic War |
E58481
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conflict in the Holy Roman Empire |
C10602
|
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: conflict in the Holy Roman Empire Context triple: [Schmalkaldic War, instanceOf, conflict in the Holy Roman Empire]
-
A.
imperial state of the Holy Roman Empire
An imperial state of the Holy Roman Empire was a semi-autonomous political entity—such as a duchy, principality, city, or ecclesiastical territory—directly subject to the authority of the emperor and the imperial diet rather than to any intermediate lord.
-
B.
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.
-
C.
English civil war
The English Civil War was a series of mid-17th-century conflicts between Parliamentarians and Royalists over political power, religion, and the authority of the monarchy, culminating in the temporary overthrow of the English crown.
-
D.
imperial confederation
An imperial confederation is a loose union of semi-autonomous states or territories under the overarching authority of an empire, which coordinates common policies while allowing substantial local self-rule.
-
E.
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.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
Created at: March 6, 2026, 9:55 p.m.