Triple
T22120301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Normandy–Flanders alliance |
E546647
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | dynastic alliance |
C45828
|
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 alliance Context triple: [Normandy–Flanders alliance, instanceOf, dynastic 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.
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.
-
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 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 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.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:31 p.m.