Triple

T1276381
Position Surface form Disambiguated ID Type / Status
Subject Elijah E27221 entity
Predicate didNotExperience P9443 FINISHED
Object ordinary physical death 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: ordinary physical death | Statement: [Elijah, didNotExperience, ordinary physical death]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: didNotExperience
Context triple: [Elijah, didNotExperience, ordinary physical death]
  • A. didNotOverrule
    Indicates that one entity, typically a higher authority or court, chose not to overturn, reverse, or invalidate the decision or ruling made by another entity.
  • B. didNotHold
    Indicates that an expected event, condition, or relationship failed to occur or be valid.
  • C. doesNot
    Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
  • D. allowsNoPriorExperience
    Indicates that the action, role, or opportunity does not require any previous experience from the participant or applicant.
  • E. notObservedIn chosen
    Indicates that a particular entity, event, or property has not been detected, recorded, or seen within a specified context, dataset, or environment.
  • 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_69a496d3710c8190955dee8bc0dacb50 completed March 1, 2026, 7:43 p.m.
NER Named-entity recognition batch_69a4c31602b8819087a57e8d390cae7a completed March 1, 2026, 10:52 p.m.
PD Predicate disambiguation batch_69a4bee0be808190a8ccac6a41851fdd completed March 1, 2026, 10:34 p.m.
Created at: March 1, 2026, 7:50 p.m.