Triple
T14796844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekuona |
E347802
|
entity |
| Predicate | hasKinshipRule |
P2846
|
FINISHED |
| Object | exogamous marriage with other Akan clans |
—
|
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: exogamous marriage with other Akan clans | Statement: [Ekuona, hasKinshipRule, exogamous marriage with other Akan clans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKinshipRule Context triple: [Ekuona, hasKinshipRule, exogamous marriage with other Akan clans]
-
A.
usesKinshipSystem
Indicates that one entity organizes or interprets familial relationships according to the kinship classification system associated with another entity.
-
B.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
C.
hasGenealogicalRelation
Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
-
D.
hasFamilyRelationContext
Indicates that there exists a family-based relationship or kinship context connecting the referenced entities.
-
E.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd5fdd548190a2ee5e668c2b20b4 |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.