Triple
T34702573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabbi Yechiel Michel Epstein |
E1000413
|
entity |
| Predicate | rabbinicPosition |
P16856
|
FINISHED |
| Object | rabbi of Novogrudok |
—
|
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: rabbi of Novogrudok | Statement: [Rabbi Yechiel Michel Epstein, rabbinicPosition, rabbi of Novogrudok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rabbinicPosition Context triple: [Rabbi Yechiel Michel Epstein, rabbinicPosition, rabbi of Novogrudok]
-
A.
roleInJudaism
chosen
Indicates the specific religious, social, or institutional function an entity holds within the context of Judaism.
-
B.
rabbinicSource
Indicates that one entity serves as a rabbinic or Talmudic source or authority for the other.
-
C.
rabbinicTradition
Indicates that something is part of, derived from, or in accordance with the teachings, interpretations, or practices of rabbinic Jewish tradition.
-
D.
positionInTalmud
Indicates the specific location or ordering of a passage, topic, or element within the structured text of the Talmud.
-
E.
statusInRabbinicLiterature
Indicates how a person, concept, or text is regarded, classified, or treated within rabbinic literature and tradition.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.