Triple
T14347405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabbi Meir |
E355761
|
entity |
| Predicate | roleInMishnah |
P16856
|
FINISHED |
| Object | one of the most frequently cited sages in the Mishnah |
—
|
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: one of the most frequently cited sages in the Mishnah | Statement: [Rabbi Meir, roleInMishnah, one of the most frequently cited sages in the Mishnah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMishnah Context triple: [Rabbi Meir, roleInMishnah, one of the most frequently cited sages in the Mishnah]
-
A.
roleInTalmud
Indicates that one entity holds a specific role, function, or status within the context of the Talmud.
-
B.
roleInJudaism
chosen
Indicates the specific religious, social, or institutional function an entity holds within the context of Judaism.
-
C.
roleInHalacha
Indicates the specific function, status, or authority an entity holds within the framework of Jewish law (halacha).
-
D.
positionInMishnehTorah
Indicates the specific location or ordering of a given item within the structure of the Mishneh Torah text.
-
E.
positionInMishnahOrders
Indicates the specific ordinal position that something occupies within the sequence of Mishnah orders.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e8b81bc8190ace2a575faf55cc0 |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.