Triple
T31248582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | יששכר |
E796753
|
entity |
| Predicate | מסורת חז"ל |
P171633
|
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.
halakhicSource
Indicates a relationship where one item serves as the halakhic (Jewish legal) basis, authority, or source text for another.
-
D.
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.
-
E.
inHalachicCanon
Indicates that something is included within, recognized by, or governed according to the authoritative body of Jewish halachic (legal) texts.
- 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_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 9:11 p.m.