Triple
T14436646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kemble family–Gage family |
E357979
|
entity |
| Predicate | hasAllianceType |
P9451
|
FINISHED |
| Object | marital alliance |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: marital alliance | Statement: [Kemble family–Gage family, hasAllianceType, marital alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAllianceType Context triple: [Kemble family–Gage family, hasAllianceType, marital alliance]
-
A.
allianceType
chosen
Indicates the specific kind or category of alliance relationship that exists between entities.
-
B.
hasAllianceInState
Indicates that an alliance or cooperative relationship exists between entities within a specified state or jurisdiction.
-
C.
allianceCompatibility
Indicates that two or more entities are suitable or well-matched to form or maintain an alliance based on their respective attributes, goals, or constraints.
-
D.
allianceStatus
Indicates the formal or informal cooperative relationship between entities, such as whether they are allies, neutral, or adversarial.
-
E.
hasAllianceFocus
Indicates that an entity is oriented toward, prioritizes, or concentrates its efforts on maintaining or developing an alliance relationship with another entity.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69de9148cf4481909082cc91b2f76218 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.