Triple
T7209236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayit Chadash |
E148755
|
entity |
| Predicate | roleInHalacha |
P75458
|
FINISHED |
| Object | major commentary on the Tur |
—
|
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: major commentary on the Tur | Statement: [Bayit Chadash, roleInHalacha, major commentary on the Tur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInHalacha Context triple: [Bayit Chadash, roleInHalacha, major commentary on the Tur]
-
A.
roleInJudaism
Indicates the specific religious, social, or institutional function an entity holds within the context of Judaism.
-
B.
halachicSection
Indicates a relationship where a subject is classified under, or associated with, a specific section or subdivision within halachic (Jewish legal) texts or rulings.
-
C.
halachicCategory
Indicates the classification of something according to Jewish legal (halachic) categories or rulings.
-
D.
stanceOnJudaism
Indicates an entity’s expressed attitude, position, or viewpoint toward Judaism.
-
E.
ordinationAsRabbi
Indicates that an individual has been formally ordained and recognized with the religious status and authority of a rabbi.
- 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_69c687e8cf188190b5f3ecffd681f04e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e96c46dc819080a6b40456d7b068 |
completed | March 27, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e889854481908c765ce2107f2d3a |
completed | March 27, 2026, 8:28 p.m. |
Created at: March 27, 2026, 2:52 p.m.