Triple
T6479499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Copenhagen (1468–1470 marriage arrangements) |
E146152
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | marriage treaty |
C566
|
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: marriage treaty Context triple: [Treaty of Copenhagen (1468–1470 marriage arrangements), instanceOf, marriage treaty]
-
A.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
B.
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.
-
C.
marriageEvent
A marriageEvent represents a specific ceremony or legal occasion in which two individuals formally enter into a marital union, capturing its participants, time, place, and related cultural or legal details.
-
D.
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.
-
E.
royal wedding
A royal wedding is a highly ceremonial marriage event involving members of a royal family, characterized by elaborate traditions, public interest, and significant cultural and political symbolism.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 4:51 p.m.