Triple

T38442739
Position Surface form Disambiguated ID Type / Status
Subject Suba people E906541 entity
Predicate hasIntermarriageWith P203339 FINISHED
Object Luo people NE NERFINISHED

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: Luo people | Statement: [Suba people, hasIntermarriageWith, Luo people]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasIntermarriageWith
Context triple: [Suba people, hasIntermarriageWith, Luo people]
  • A. connectedThroughMarriageVia
    Indicates that two entities are related to each other by a marital connection that is mediated through one or more intermediate spouses or in-laws, rather than by a direct marriage between them.
  • B. formedByMarriageOf
    Indicates that something (typically a family, union, or legal entity) comes into existence as a result of the marriage between two entities.
  • C. marriedOutsideRoyalty
    Indicates that a person entered into marriage with someone who is not a member of a royal family.
  • D. marriedBy
    Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
  • E. ethnicGroupByMarriage
    Indicates a relationship where an individual's ethnic group is determined or associated through marriage rather than by birth or ancestry.
  • 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_69f76e72878c8190a692836c8b01b58b completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a016336c58081909c58c5772e6fb488 completed May 11, 2026, 5:03 a.m.
PD Predicate disambiguation batch_6a0160f25d8081909a6aaa375e9850b0 completed May 11, 2026, 4:54 a.m.
PDg Predicate description generation batch_6a0163359e588190ba365f65b2d86435 completed May 11, 2026, 5:03 a.m.
Created at: May 3, 2026, 4:31 p.m.