Triple

T457886
Position Surface form Disambiguated ID Type / Status
Subject Yom Ha’atzmaut E7271 entity
Predicate religiousPractice P2154 FINISHED
Object recitation of Hallel in some communities 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: recitation of Hallel in some communities | Statement: [Yom Ha’atzmaut, religiousPractice, recitation of Hallel in some communities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: religiousPractice
Context triple: [Yom Ha’atzmaut, religiousPractice, recitation of Hallel in some communities]
  • A. religiousFunction
    Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
  • B. religiousElement chosen
    Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
  • C. religiousTarget
    Indicates that an action, policy, or behavior is directed at someone or something specifically because of their religion or religious affiliation.
  • D. otherReligion
    Indicates that one entity follows or is associated with a religion that is different from the religion of another entity.
  • E. religiousAffiliation
    Indicates that one entity has a specified religious association, belief system, or denominational membership.
  • 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_69a2e7e5c5bc8190a1dc8178218fba40 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2efa3163081909acff040a22bd559 completed Feb. 28, 2026, 1:37 p.m.
PD Predicate disambiguation batch_69a2ede614b88190be07425f5535f56d completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.