Triple
T32346387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torah Lishmah |
E826470
|
entity |
| Predicate | halachicAuthority |
P174174
|
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: [Torah Lishmah, halachicAuthority, Ben Ish Chai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: halachicAuthority Context triple: [Torah Lishmah, halachicAuthority, Ben Ish Chai]
-
A.
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.
-
B.
inHalachicCanon
Indicates that something is included within, recognized by, or governed according to the authoritative body of Jewish halachic (legal) texts.
-
C.
halakhicFunction
Indicates a relationship where something serves a role, purpose, or effect within the framework of Jewish law (halakha).
-
D.
halachicTopic
Indicates that something is related to, concerns, or falls under a particular topic within Jewish law (halacha).
-
E.
halachicCategory
Indicates the classification of something according to Jewish legal (halachic) categories or rulings.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be52a40c8190a98066f81bed2d67 |
completed | May 3, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:48 a.m.