Triple
T1308446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishnah Berurah |
E27933
|
entity |
| Predicate | subject |
P450
|
FINISHED |
| Object | Orach Chayim |
E148752
|
NE 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: Orach Chayim | Statement: [Mishnah Berurah, subject, Orach Chayim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orach Chayim Context triple: [Mishnah Berurah, subject, Orach Chayim]
-
A.
Orach Chayim
chosen
Orach Chayim is a section of Jewish law that primarily deals with daily religious practices, prayer, Shabbat, and festivals.
-
B.
Shir Shel Yom
Shir Shel Yom is the daily Psalm recited in Jewish prayer services, with a specific psalm designated for each day of the week.
-
C.
Har HaMenuchot
Har HaMenuchot is a major Jewish cemetery in Jerusalem, serving as one of the city's primary burial grounds since the mid-20th century.
-
D.
Sha'arei Orah
Sha'arei Orah is a seminal Kabbalistic work that systematically explains the divine names and sefirot within Jewish mysticism.
-
E.
Imrei Shefer
Imrei Shefer is a mystical work by the 13th-century Kabbalist Abraham Abulafia, reflecting his prophetic and ecstatic Kabbalistic teachings.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c13806b48190a0db33f8e5d53734 |
completed | March 1, 2026, 10:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acbaec736881909645919764d73f5f |
completed | March 7, 2026, 11:55 p.m. |
Created at: March 1, 2026, 7:51 p.m.