Triple
T22290837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hohenstaufen–Plantagenet dynastic alliance |
E550989
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | marital alliance |
C46061
|
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: marital alliance Context triple: [Hohenstaufen–Plantagenet dynastic alliance, instanceOf, marital alliance]
-
A.
dynastic union
A dynastic union is a political arrangement in which two or more separate states are ruled by the same monarch due to inheritance or marriage, while each state retains its own laws and institutions.
-
B.
historical alliance
A historical alliance is a formal or informal partnership between states, groups, or leaders formed in the past to pursue shared political, military, economic, or cultural goals.
-
C.
political-military alliance
A political-military alliance is a formal agreement between two or more states to coordinate their defense and foreign policies, often including mutual security guarantees and joint military planning.
-
D.
treaty-based alliance
A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
-
E.
noble house membership by marriage
A noble house membership by marriage represents an individual's affiliation and acquired status within a noble lineage gained through legally recognized marital union rather than by birth.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:41 p.m.