Triple
T13197370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nassau Family Pact |
E314148
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | dynastic pact |
C27712
|
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 pact Context triple: [Nassau Family Pact, instanceOf, dynastic pact]
-
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.
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.
-
C.
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.
-
D.
dynastic office
A dynastic office is a formal position of authority or responsibility that is inherited within a family line, typically passing from one generation to the next.
-
E.
medieval political agreement
chosen
A medieval political agreement is a formal or informal pact between rulers, nobles, or institutions that defines mutual obligations—such as protection, allegiance, tribute, or territorial control—within the feudal and dynastic power structures of the Middle Ages.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:16 p.m.