Triple
T3742778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beit midrash |
E79739
|
entity |
| Predicate | relatedConcept |
P37
|
FINISHED |
| Object | Beit din |
E79746
|
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: Beit din | Statement: [Beit midrash, relatedConcept, Beit din]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beit din Context triple: [Beit midrash, relatedConcept, Beit din]
-
A.
Beit din
chosen
Beit din is a rabbinical court in Judaism that adjudicates matters of religious law, personal status, and communal disputes.
-
B.
Beit Yosef
Beit Yosef is a comprehensive halachic commentary on the Arba'ah Turim by Rabbi Yosef Karo, serving as the primary source and foundation for his later code, the Shulchan Aruch.
-
C.
Beit HaNassi
Beit HaNassi is the official residence and ceremonial home of the President of Israel, located in Jerusalem.
-
D.
Beit Shmuel
Beit Shmuel is a classic halachic commentary on the Even Ha’ezer section of the Shulchan Aruch, widely studied in traditional Jewish legal scholarship.
-
E.
Beit Hanina
Beit Hanina is a Palestinian neighborhood in northern East Jerusalem, known as a primarily residential area with a mix of urban development and traditional community life.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb563fac8190b6a55580d0386e8a |
completed | March 8, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4db29b2288190932923a6bf1a7e8e |
completed | March 14, 2026, 3:51 a.m. |
Created at: March 8, 2026, 3:34 p.m.