Triple

T23987036
Position Surface form Disambiguated ID Type / Status
Subject Sephardi and Mizrahi Jews E604965 entity
Predicate usesReligiousLegalCode P3013 FINISHED
Object Ben Ish Chai 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: Ben Ish Chai | Statement: [Sephardi and Mizrahi Jews, usesReligiousLegalCode, Ben Ish Chai]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesReligiousLegalCode
Context triple: [Sephardi and Mizrahi Jews, usesReligiousLegalCode, Ben Ish Chai]
  • A. religiousLawAspect
    Indicates that one entity represents a specific aspect, dimension, or component of a religious law associated with another entity.
  • B. religiousJurisdiction
    Indicates that one entity holds official religious authority or governance over another entity or area.
  • C. religiousLawView
    Indicates a person's stance, interpretation, or opinion regarding a particular religious law or set of religious legal principles.
  • D. usesLegalCode chosen
    Indicates that one entity applies, references, or operates under a particular legal code in its actions or regulations.
  • E. hasReligiousNorm
    Indicates that one entity prescribes, embodies, or is governed by a religious rule, standard, or expectation in relation to another entity or context.
  • 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_69e295463f7c8190b1c19dbd114641b9 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f1d38838f481909a52fccd392a92df completed April 29, 2026, 9:46 a.m.
PD Predicate disambiguation batch_69f161578d54819084a8b35496299993 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 9:36 p.m.