Triple

T22362057
Position Surface form Disambiguated ID Type / Status
Subject Hashkivenu E552800 entity
Predicate relatedPrayer P21327 FINISHED
Object Sim Shalom 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: Sim Shalom | Statement: [Hashkivenu, relatedPrayer, Sim Shalom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sim Shalom
Context triple: [Hashkivenu, relatedPrayer, Sim Shalom]
  • A. Sim Shalom chosen
    Sim Shalom is a Jewish liturgical prayer that asks God to grant peace, blessing, and goodness to the people of Israel.
  • B. Sashalom
    Sashalom is a residential neighborhood in the 16th district of Budapest, Hungary.
  • C. Shalom
    Shalom is a Hebrew given name commonly used in Jewish communities, meaning "peace" and often symbolizing harmony and well-being.
  • D. Shalom Rav
    Shalom Rav is a Jewish liturgical prayer asking God for abundant peace, traditionally recited during the Amidah in Ashkenazi communities at Mincha and Ma'ariv.
  • E. Ma'ale HaShalom
    Ma'ale HaShalom is a road in Jerusalem that connects the Dung Gate area of the Old City with surrounding neighborhoods and access routes.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e4affcc8190ba7c27d29062558d completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f157d44a908190b16e4cfdf4591b10 completed April 29, 2026, 12:59 a.m.
Created at: April 16, 2026, 8:44 p.m.