Triple
T9384734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese succession crisis of 1580 |
E225876
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | dynastic succession crisis |
C473
|
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: dynastic succession crisis Context triple: [Portuguese succession crisis of 1580, instanceOf, dynastic succession crisis]
-
A.
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.
-
B.
succession war
chosen
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.
-
C.
act of succession
An act of succession is a formal event or process by which authority, title, or position is transferred from one holder to another, establishing a new legitimate bearer.
-
D.
dynastic empire
A dynastic empire is a vast, centralized state ruled over generations by a single family lineage that legitimizes its authority through hereditary succession and often divine or traditional claims to power.
-
E.
dynastic branch
A dynastic branch is a subordinate line of a ruling or noble family that descends from a common ancestor but forms its own distinct lineage within the broader dynasty.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:44 p.m.