Triple
T13376797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rav Ashi |
E319207
|
entity |
| Predicate | roleInTalmud |
P109675
|
FINISHED |
| Object | editor |
—
|
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: editor | Statement: [Rav Ashi, roleInTalmud, editor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTalmud Context triple: [Rav Ashi, roleInTalmud, editor]
-
A.
roleInJudaism
Indicates the specific religious, social, or institutional function an entity holds within the context of Judaism.
-
B.
roleInHalacha
Indicates the specific function, status, or authority an entity holds within the framework of Jewish law (halacha).
-
C.
positionInTalmud
Indicates the specific location or ordering of a passage, topic, or element within the structured text of the Talmud.
-
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.
eraWithinJudaism
Indicates that a time period or era occurs within, or is defined as part of, the broader historical or religious framework of Judaism.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce3fec48190a5443d87c85477a3 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:33 p.m.