Triple
T21185776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bnei Menashe |
E522073
|
entity |
| Predicate | religiousStatusInIsrael |
P89144
|
FINISHED |
| Object | subject to Chief Rabbinate rulings |
—
|
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: subject to Chief Rabbinate rulings | Statement: [Bnei Menashe, religiousStatusInIsrael, subject to Chief Rabbinate rulings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousStatusInIsrael Context triple: [Bnei Menashe, religiousStatusInIsrael, subject to Chief Rabbinate rulings]
-
A.
religiousStatus
Indicates the religious affiliation, role, or standing that an entity holds within a religious context.
-
B.
statusUnderIsraeliLaw
chosen
Indicates the legal standing or classification an entity holds according to Israeli law.
-
C.
statusOfJerusalem
Indicates the political or legal condition, control, or recognition of Jerusalem at a given time.
-
D.
schoolStatusInIsrael
Indicates the educational status or situation of an entity within the school system in Israel.
-
E.
roleInIsrael
Indicates that an entity holds or held a specific role, position, or function within the context of Israel.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73021671c8190a7b464ece7dbaadd |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:06 p.m.