Triple

T11147181
Position Surface form Disambiguated ID Type / Status
Subject Kinnim E263697 entity
Predicate hasTalmudBavli P95908 FINISHED
Object no 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 | Statement: [Kinnim, hasTalmudBavli, no]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTalmudBavli
Context triple: [Kinnim, hasTalmudBavli, no]
  • A. hasGemara
    Indicates that an entity possesses, includes, or is associated with a Gemara (a Talmudic text or study component).
  • B. hasJerusalemTalmud
    Indicates that an entity possesses, is associated with, or is characterized by the Jerusalem Talmud.
  • C. hasNoBavliGemaraForMostTractates chosen
    Indicates that there is no Babylonian Talmud (Bavli) Gemara text available for the majority of the tractates in question.
  • D. includesMegillot
    Indicates that one entity contains or encompasses the set of texts or items referred to as Megillot.
  • E. halakhicSource
    Indicates a relationship where one item serves as the halakhic (Jewish legal) basis, authority, or source text for another.
  • 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_69d6aa9ccddc8190868998c8b7beb060 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e86e9ef48190b4df4b14319a954f completed April 9, 2026, 5:57 p.m.
PD Predicate disambiguation batch_69d75ce104908190b6cc31ef2f67846a completed April 9, 2026, 8:01 a.m.
Created at: April 8, 2026, 9:28 p.m.