Triple
T34572198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negaim |
E887653
|
entity |
| Predicate | talmudBavliStatus |
P95908
|
FINISHED |
| Object | no Babylonian Talmud Gemara |
—
|
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: no Babylonian Talmud Gemara | Statement: [Negaim, talmudBavliStatus, no Babylonian Talmud Gemara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: talmudBavliStatus Context triple: [Negaim, talmudBavliStatus, no Babylonian Talmud Gemara]
-
A.
hasBabylonianTalmudPagesApprox
Indicates an approximate number of pages attributed to an entity in the Babylonian Talmud.
-
B.
hasGemara
Indicates that an entity possesses, includes, or is associated with a Gemara (a Talmudic text or study component).
-
C.
hasNoBavliGemaraForMostTractates
chosen
Indicates that there is no Babylonian Talmud (Bavli) Gemara text available for the majority of the tractates in question.
-
D.
positionInTalmud
Indicates the specific location or ordering of a passage, topic, or element within the structured text of the Talmud.
-
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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720965c9881908f0ea7e17fc2c1be |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:03 a.m.