Triple

T7394899
Position Surface form Disambiguated ID Type / Status
Subject Menachem E170596 entity
Predicate hasNameDayOrReligiousUsage P76329 FINISHED
Object used in Jewish religious 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: used in Jewish religious communities | Statement: [Menachem, hasNameDayOrReligiousUsage, used in Jewish religious communities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNameDayOrReligiousUsage
Context triple: [Menachem, hasNameDayOrReligiousUsage, used in Jewish religious communities]
  • A. hasNameDay
    Indicates that an entity is associated with a specific date on which its name is traditionally celebrated (a name day).
  • B. hasNameDayRelation
    Indicates a relationship where a person’s name is associated with a specific name day or feast day in a calendar.
  • C. religiousNamesake
    Indicates that one entity serves as the religiously significant figure, concept, or object after which the other entity is named.
  • D. hasNameDayContext
    Indicates that an entity’s name day is interpreted or celebrated within a specific contextual framework (such as culture, calendar system, or tradition).
  • E. hasLiturgicalName
    Indicates that an entity is associated with a specific name used in liturgical or religious worship contexts.
  • F. None of above. chosen

Provenance (4 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_69c68a5f04188190ac266569c9280347 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f2279de4819081b8876d02f55388 completed March 27, 2026, 9:09 p.m.
PD Predicate disambiguation batch_69c6f0309cc88190b55d278969400294 completed March 27, 2026, 9:01 p.m.
PDg Predicate description generation batch_69c6f0be2b1c8190bea06100a7caef2b completed March 27, 2026, 9:03 p.m.
Created at: March 27, 2026, 3:09 p.m.