Triple

T31104718
Position Surface form Disambiguated ID Type / Status
Subject Mother of the Kwisatz Haderach E792762 entity
Predicate typicalAllegiance P207354 FINISHED
Object Bene Gesserit long-term plans 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: Bene Gesserit long-term plans | Statement: [Mother of the Kwisatz Haderach, typicalAllegiance, Bene Gesserit long-term plans]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalAllegiance
Context triple: [Mother of the Kwisatz Haderach, typicalAllegiance, Bene Gesserit long-term plans]
  • A. namedForAllegiance
    Indicates that an entity is named in reference to, or in honor of, a particular allegiance, affiliation, or loyalty.
  • B. countryOfAllegiance
    Indicates the country to which an entity owes loyalty, support, or official allegiance.
  • C. stateAllegiance
    Indicates that one entity formally declares loyalty or support to another entity, such as a person, group, or state.
  • D. hadAllegiance
    Indicates that an entity was loyally committed or formally bound in support or service to another entity, such as a person, group, or cause.
  • E. allegiance
    Indicates a relationship where one entity is loyal, committed, or obligated in support or service to another entity.
  • 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_69f224cfd5d881908ec6447bc321cd58 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_6a037c9141dc819098d7fcc36e69882c completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379e5174c8190a0bdde7e381b7624 completed May 12, 2026, 7:05 p.m.
PDg Predicate description generation batch_6a037c7ee0388190a29faeb5cdb0950a completed May 12, 2026, 7:16 p.m.
Created at: April 29, 2026, 9:03 p.m.