Triple

T30740894
Position Surface form Disambiguated ID Type / Status
Subject Ammaron E782686 entity
Predicate successorAsRecordKeeper P92254 FINISHED
Object Mormon 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: Mormon | Statement: [Ammaron, successorAsRecordKeeper, Mormon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: successorAsRecordKeeper
Context triple: [Ammaron, successorAsRecordKeeper, Mormon]
  • A. successorInPractice
    Indicates that one entity has taken over the role, position, or function of another in actual practice, even if not formally or officially designated as its successor.
  • B. successorReceives
    Indicates that a successor entity obtains or is granted something (such as rights, assets, or responsibilities) from a predecessor.
  • C. successorDeterminedBy
    Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
  • D. successorRole
    Indicates that one role or position directly follows and replaces another in a sequence or organizational structure.
  • E. regardsAsRightfulSuccessorOf chosen
    Indicates that one entity recognizes or treats another entity as the legitimate heir or next in line to assume a particular role, position, or status.
  • 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_69fea1f5d8c481908dc3351dc9ecef7f completed May 9, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69fea06b6fe0819095bf4c1bc9809927 completed May 9, 2026, 2:48 a.m.
Created at: April 29, 2026, 8:38 p.m.