Triple

T30741198
Position Surface form Disambiguated ID Type / Status
Subject the brother of Jared E782692 entity
Predicate hasNameInLDSTradition P17611 FINISHED
Object Mahonri Moriancumer 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: Mahonri Moriancumer | Statement: [the brother of Jared, hasNameInLDSTradition, Mahonri Moriancumer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNameInLDSTradition
Context triple: [the brother of Jared, hasNameInLDSTradition, Mahonri Moriancumer]
  • A. hasLiturgicalName
    Indicates that an entity is associated with a specific name used in liturgical or religious worship contexts.
  • B. hasTraditionalName chosen
    Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
  • C. nameInWesternTradition
    Indicates that an entity’s name is expressed following Western naming conventions, typically with the given name preceding the family name.
  • D. hasReligiousName
    Indicates that an entity possesses a name specifically associated with a religious context, role, or tradition.
  • E. belongsToNamingTradition
    Indicates that an entity is associated with or classified under a particular naming tradition or convention.
  • 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_69f224aeb1588190897d395e8ed2acb8 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fde9fc184c8190bebef35df0e76076 completed May 8, 2026, 1:49 p.m.
PD Predicate disambiguation batch_69fde6e5beb4819094945a695e961d88 completed May 8, 2026, 1:36 p.m.
Created at: April 29, 2026, 8:38 p.m.