Triple
T21957155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Wars (medieval Angevin conflicts in Italy) |
E542221
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | series of dynastic wars |
C14491
|
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: series of dynastic wars Context triple: [Italian Wars (medieval Angevin conflicts in Italy), instanceOf, series of dynastic wars]
-
A.
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.
-
B.
period of warfare
A period of warfare is a span of time characterized by sustained armed conflict between organized groups, typically involving military operations, political objectives, and significant social and economic disruption.
-
C.
series of conflicts
A series of conflicts is a sequence of interconnected disputes, struggles, or confrontations that unfold over time, often escalating or evolving as parties respond to previous clashes.
-
D.
dynastic rivalry
Dynastic rivalry is the sustained political, military, and familial competition between ruling houses or lineages for supremacy, legitimacy, and control over territories or thrones.
-
E.
Italian Wars
chosen
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.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:59 p.m.