Triple
T13705198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | שֵׁת |
E328620
|
entity |
| Predicate | מסורת מדרשית |
P111247
|
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.
halakhicSource
Indicates a relationship where one item serves as the halakhic (Jewish legal) basis, authority, or source text for another.
-
B.
eraWithinJudaism
Indicates that a time period or era occurs within, or is defined as part of, the broader historical or religious framework of Judaism.
-
C.
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.
-
D.
halakhicApproach
Indicates an entity’s method, stance, or interpretive framework for applying or understanding Jewish law (halakha) in practice.
-
E.
rabbinicSource
Indicates that one entity serves as a rabbinic or Talmudic source or authority for the other.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad17732c8190bbd0d73107711c99 |
completed | April 13, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:54 p.m.