Triple
T24138012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makua people |
E598142
|
entity |
| Predicate | descentRule |
P23527
|
FINISHED |
| Object | matrilineal descent |
—
|
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: matrilineal descent | Statement: [Makua people, descentRule, matrilineal descent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: descentRule Context triple: [Makua people, descentRule, matrilineal descent]
-
A.
followsDescentRule
Indicates that the relationship or action proceeds according to a specified rule of descent, such as inheritance or derivation from a prior source.
-
B.
descentVia
Indicates a lineage relationship where one entity is descended from another through one or more intermediate generations or branches.
-
C.
descentSystem
chosen
Indicates the kinship or inheritance pattern through which lineage, membership, or rights are traced (e.g., matrilineal, patrilineal, or bilateral).
-
D.
descentFrom
Indicates that one entity is a descendant of another, typically through a lineage or ancestral relationship.
-
E.
descentMethod
Indicates the technique or process used to descend from a higher position, level, or altitude.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7e3c20819099ff289789829d7e |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:27 p.m.