Triple
T26039147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis XIV's wars |
E647637
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European military conflicts |
C46937
|
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: European military conflicts Context triple: [Louis XIV's wars, instanceOf, European military conflicts]
-
A.
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.
-
B.
early modern European conflicts
chosen
Early modern European conflicts encompass the interconnected wars, rebellions, and power struggles from roughly the late 15th to the early 18th century that reshaped political boundaries, religious alignments, and state structures across the continent.
-
C.
Italian Wars
The Italian Wars were a series of conflicts from 1494 to 1559 in which major European powers fought for control of the Italian peninsula, reshaping Renaissance politics, warfare, and diplomacy.
-
D.
Byzantine–Germanic wars
The Byzantine–Germanic wars were a series of military conflicts between the Eastern Roman (Byzantine) Empire and various Germanic kingdoms in Western Europe, primarily during the 5th to 7th centuries, as the Byzantines sought to reclaim former Roman territories.
-
E.
Ottoman–Habsburg wars
The Ottoman–Habsburg wars were a series of military conflicts from the 16th to the 18th centuries between the Ottoman Empire and the Habsburg Monarchy for dominance in Central and Southeastern Europe.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:08 a.m.