Triple

T157392
Position Surface form Disambiguated ID Type / Status
Subject Triumphal Entry into Jerusalem E3208 entity
Predicate fulfillsProphecy P4233 FINISHED
Object Zechariah 9:9 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: Zechariah 9:9 | Statement: [Triumphal Entry into Jerusalem, fulfillsProphecy, Zechariah 9:9]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fulfillsProphecy
Context triple: [Triumphal Entry into Jerusalem, fulfillsProphecy, Zechariah 9:9]
  • A. satisfies chosen
    Indicates that one entity meets, fulfills, or complies with the requirements, conditions, or expectations specified by another.
  • B. ensures
    Indicates that one entity guarantees or makes certain that a particular condition, outcome, or state holds for another entity or situation.
  • C. oath
    Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
  • D. appointedFor
    Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
  • E. affirms
    Indicates that one entity explicitly confirms, supports, or asserts the truth or validity of another entity, statement, or proposition.
  • 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_69a2527757ec819090b8becb2cf1a862 completed Feb. 28, 2026, 2:27 a.m.
NER Named-entity recognition batch_69a25830136881909f5ecb2cb22097b2 completed Feb. 28, 2026, 2:51 a.m.
PD Predicate disambiguation batch_69a2565f30848190a2a71fdb7dc140b5 completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:31 a.m.