Triple
T25395713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabbeinu Asher |
E636284
|
entity |
| Predicate | talmudicMethod |
P27804
|
FINISHED |
| Object | focus on practical halakhic conclusions |
—
|
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: focus on practical halakhic conclusions | Statement: [Rabbeinu Asher, talmudicMethod, focus on practical halakhic conclusions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: talmudicMethod Context triple: [Rabbeinu Asher, talmudicMethod, focus on practical halakhic conclusions]
-
A.
positionInTalmud
Indicates the specific location or ordering of a passage, topic, or element within the structured text of the Talmud.
-
B.
roleInTalmud
Indicates that one entity holds a specific role, function, or status within the context of the Talmud.
-
C.
halakhicApproach
chosen
Indicates an entity’s method, stance, or interpretive framework for applying or understanding Jewish law (halakha) in practice.
-
D.
halakhicSource
Indicates a relationship where one item serves as the halakhic (Jewish legal) basis, authority, or source text for another.
-
E.
hasJerusalemTalmud
Indicates that an entity possesses, is associated with, or is characterized by the Jerusalem Talmud.
- F. None of above.
Provenance (3 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f584f07b648190aee894c1d5320bc3 |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:49 p.m.