Triple
T7952578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bemba people |
E184650
|
entity |
| Predicate | clanInheritance |
P79992
|
FINISHED |
| Object | through the mother’s line |
—
|
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: through the mother’s line | Statement: [Bemba people, clanInheritance, through the mother’s line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanInheritance Context triple: [Bemba people, clanInheritance, through the mother’s line]
-
A.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
B.
clanType
Indicates the specific category or classification of a clan within a broader clan system or hierarchy.
-
C.
dynasticInheritance
Indicates that rights, titles, or property are passed down through a family line according to established rules of succession.
-
D.
clanChiefBranchOf
Indicates that a particular clan chief belongs to, or is a leading figure within, a specific branch or subdivision of a larger clan.
-
E.
dominantClanFamilies
Indicates that certain families hold primary power or influence within a clan relative to other families.
- F. None of above. chosen
Provenance (4 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b5c95908190b6ee900d2b324574 |
completed | March 31, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:10 p.m.