Triple
T31248588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | יששכר |
E796753
|
entity |
| Predicate | מסורת קבלית |
P172205
|
FINISHED |
| Object | מקושר למידת התורה |
—
|
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: מקושר למידת התורה | Statement: [יששכר, מסורת קבלית, מקושר למידת התורה]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: מסורת קבלית Context triple: [יששכר, מסורת קבלית, מקושר למידת התורה]
-
A.
מסורת דתית
Indicates a relationship where an entity is associated with, follows, or is characterized by a particular religious tradition.
-
B.
מסורת מדרשית
Indicates a relationship where one entity is part of, derived from, or characterized by a specific midrashic (rabbinic interpretive) tradition.
-
C.
מסורת חז"ל
Indicates the relationship in which something is based on, derived from, or in accordance with the rabbinic tradition and teachings of the Sages (Chazal).
-
D.
פרשנות מסורתית
Indicates a relationship where an entity is interpreted or understood according to traditional, established explanatory frameworks or commentaries.
-
E.
traditionalJewishOrder
Indicates that something follows or conforms to the customary or historically established order used in Jewish tradition.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 29, 2026, 9:11 p.m.