Triple

T3720888
Position Surface form Disambiguated ID Type / Status
Subject Akedah E81633 entity
Predicate hasPromise P36138 FINISHED
Object God reaffirms blessing and numerous descendants to Abraham 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: God reaffirms blessing and numerous descendants to Abraham | Statement: [Akedah, hasPromise, God reaffirms blessing and numerous descendants to Abraham]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPromise
Context triple: [Akedah, hasPromise, God reaffirms blessing and numerous descendants to Abraham]
  • A. promises
    Indicates that one entity commits to performing, providing, or ensuring something for another entity in the future.
  • B. corePromise
    Indicates the primary commitment or central obligation that one party is bound to fulfill within an agreement or relationship.
  • C. receivedPromiseAbout chosen
    Indicates that one entity has been given an assurance or commitment concerning another entity or event by some source.
  • D. hasHook
    Indicates that one entity possesses, is equipped with, or features a hook in relation to another entity or context.
  • E. hasProposedOutcome
    Indicates that an action, decision, or process is associated with a suggested or anticipated result that is being put forward but not yet realized or confirmed.
  • 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_69ad8b1b7ef081908d2d381bbf54985a completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adca9b5ca8819094299fffc02606ce completed March 8, 2026, 7:14 p.m.
PD Predicate disambiguation batch_69adc0436e508190909ec4a3e8443aef completed March 8, 2026, 6:30 p.m.
Created at: March 8, 2026, 3:34 p.m.