Triple

T4768272
Position Surface form Disambiguated ID Type / Status
Subject Huldah E105863 entity
Predicate promiseMessage P13485 FINISHED
Object Josiah would be gathered to his grave in peace 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: Josiah would be gathered to his grave in peace | Statement: [Huldah, promiseMessage, Josiah would be gathered to his grave in peace]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: promiseMessage
Context triple: [Huldah, promiseMessage, Josiah would be gathered to his grave in peace]
  • A. receivedPromiseAbout
    Indicates that one entity has been given an assurance or commitment concerning another entity or event by some source.
  • B. promises
    Indicates that one entity commits to performing, providing, or ensuring something for another entity in the future.
  • C. confirmationOutcome
    Indicates the result or status produced when a prior action, request, or assertion is checked and confirmed.
  • D. campaignPromise
    Indicates that an individual or organization has made a public commitment to take a specific action or pursue a particular policy as part of a campaign.
  • E. intendedMessage chosen
    Indicates that one entity is the message or content that another entity aims or plans to communicate.
  • 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_69bd43f226fc8190b867cc249c2a9042 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd686ef1b08190ad60375592c9d6c0 completed March 20, 2026, 3:31 p.m.
PD Predicate disambiguation batch_69bd622807f881908e4bcb14f7731bac completed March 20, 2026, 3:05 p.m.
Created at: March 20, 2026, 1:21 p.m.