Triple
T14436624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kemble family–Gage family |
E357979
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical family alliance |
C24628
|
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: historical family alliance Context triple: [Kemble family–Gage family, instanceOf, historical family alliance]
-
A.
historical alliance
chosen
A historical alliance is a formal or informal partnership between states, groups, or leaders formed in the past to pursue shared political, military, economic, or cultural goals.
-
B.
historical relationship
A historical relationship is a connection between people, groups, or entities that existed in the past and is understood through documented events, interactions, and their lasting impact over time.
-
C.
early modern political alliance
An early modern political alliance is a formal or informal agreement between states, dynasties, or political entities from roughly the 15th to 18th centuries to cooperate for mutual security, territorial, economic, or dynastic advantage within a shifting balance-of-power system.
-
D.
dynastic history
Dynastic history is the study and narrative of successive ruling families, their power transitions, political structures, and cultural impacts over time within a particular region or civilization.
-
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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:18 a.m.