Triple
T3635880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sura |
E77064
|
entity |
| Predicate | notableHead |
P1918
|
FINISHED |
| Object | Rav Chisda |
E401022
|
NE 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: Rav Chisda | Statement: [Sura, notableHead, Rav Chisda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rav Chisda Context triple: [Sura, notableHead, Rav Chisda]
-
A.
Rav Chisda
chosen
Rav Chisda was a prominent third-generation Babylonian Amora and Talmudic sage known for his sharp legal analysis and teachings in the academies of Babylonia.
-
B.
Rav Ashi
Rav Ashi was a leading Babylonian Talmudic sage traditionally credited with initiating the redaction and organization of the Babylonian Talmud.
-
C.
Rav Sheshet
Rav Sheshet was a prominent Babylonian Amoraic sage renowned for his vast Talmudic knowledge and sharp halakhic analysis.
-
D.
Rav Huna
Rav Huna was a prominent third-century Babylonian Amora and head of the Sura academy, renowned for his halakhic rulings and influence on the Talmud.
-
E.
Rav Yehuda
Rav Yehuda was a prominent early Babylonian Amoraic sage and disciple of Rav who played a key role in shaping Talmudic scholarship.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc325e2548190ae243ae69126e65c |
completed | March 8, 2026, 6:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b54c256e0881909c6d481d373e814c |
completed | March 14, 2026, 11:53 a.m. |
Created at: March 8, 2026, 3:24 p.m.