Triple
T25670392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Habsburg–Braganza marital alliances |
E643654
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | dynastic marital alliance network |
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: dynastic marital alliance network Context triple: [Habsburg–Braganza marital alliances, instanceOf, dynastic marital alliance network]
-
A.
dynastic alliance
A dynastic alliance is a political and social union formed through marriage or blood ties between ruling families to secure mutual power, succession, and strategic advantage.
-
B.
marital alliance
chosen
A marital alliance is a strategic union formed through marriage between individuals, families, or groups to secure political, economic, social, or cultural advantages.
-
C.
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.
-
D.
dynastic affiliation category
A dynastic affiliation category classifies entities—such as individuals, artifacts, or events—according to their association with a specific ruling dynasty or hereditary line of power.
-
E.
dynastic group
A dynastic group is a collection of individuals connected by hereditary lineage who collectively hold, inherit, or exercise enduring social, political, or economic power across generations.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 7:26 p.m.