Triple

T36205504
Position Surface form Disambiguated ID Type / Status
Subject Padang Dinka subgroup E1047386 entity
Predicate hasMarriageSystem P204105 FINISHED
Object exogamous clan marriage rules 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 clan marriage rules | Statement: [Padang Dinka subgroup, hasMarriageSystem, exogamous clan marriage rules]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMarriageSystem
Context triple: [Padang Dinka subgroup, hasMarriageSystem, exogamous clan marriage rules]
  • A. hasMarriage
    Indicates a marital relationship exists between the two entities, specifying that they are or were legally married to each other.
  • B. hasMarriagePlot
    Indicates that the work’s narrative centrally involves courtship, romantic relationships, or the progression toward marriage as a key plot element.
  • C. marriageType
    Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
  • D. hasMaritalFunction
    Indicates that one entity serves a role or performs a function within the context of a marital relationship or institution.
  • E. marriesFor
    Indicates that one entity enters into marriage with another entity specifically for a particular reason, motive, or benefit.
  • 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_69f76e414bdc8190996f15a544220a3d completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a0324c2d618819093f7e6424b0f5baf completed May 12, 2026, 1:01 p.m.
PD Predicate disambiguation batch_6a0324292e588190b37d0c3016ea2062 completed May 12, 2026, 12:59 p.m.
PDg Predicate description generation batch_6a0324c1f89881909fc713e93e9c5f1c completed May 12, 2026, 1:01 p.m.
Created at: May 3, 2026, 4:08 p.m.