Triple
T24076968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | marriage of James III of Scotland and Margaret of Denmark |
E596391
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | dynastic marriage |
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 marriage Context triple: [marriage of James III of Scotland and Margaret of Denmark, instanceOf, dynastic marriage]
-
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.
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.
-
C.
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.
-
D.
dynastic pledge
A dynastic pledge is a formal, often hereditary commitment between ruling families or lineages—such as through marriage, alliance, or succession agreements—intended to secure long-term political stability and mutual obligation across generations.
-
E.
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.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 10:42 p.m.