Triple

T8209418
Position Surface form Disambiguated ID Type / Status
Subject Tongass people E191775 entity
Predicate kinshipDescent 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: [Tongass people, kinshipDescent, matrilineal descent]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: kinshipDescent
Context triple: [Tongass people, kinshipDescent, matrilineal descent]
  • A. descentSystem chosen
    Indicates the kinship or inheritance pattern through which lineage, membership, or rights are traced (e.g., matrilineal, patrilineal, or bilateral).
  • B. patriarchalLineage
    Indicates a familial relationship where descent, inheritance, or identity is traced through the male line or father’s ancestry.
  • C. claimedDescentFrom
    Indicates that one entity asserts or maintains that it is descended from, or originates genealogically from, another entity.
  • D. clanInheritance
    Indicates that rights, titles, or property are passed down within a clan according to its internal rules of succession.
  • E. ancestralGroup
    Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
  • 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_69ca82c8c054819087fedd9a5436b8a3 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb76dc784881908e1f63ac907cdd01 completed March 31, 2026, 7:25 a.m.
PD Predicate disambiguation batch_69cb36ad01ac81909609b15f6a6c8581 completed March 31, 2026, 2:51 a.m.
Created at: March 30, 2026, 5:44 p.m.