Triple

T23853152
Position Surface form Disambiguated ID Type / Status
Subject Sukkah E592226 entity
Predicate halakhicCodeDiscussedIn P17762 FINISHED
Object Mishnah Sukkah NE NERFINISHED

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: Mishnah Sukkah | Statement: [Sukkah, halakhicCodeDiscussedIn, Mishnah Sukkah]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: halakhicCodeDiscussedIn
Context triple: [Sukkah, halakhicCodeDiscussedIn, Mishnah Sukkah]
  • A. halakhicSource chosen
    Indicates a relationship where one item serves as the halakhic (Jewish legal) basis, authority, or source text for another.
  • B. halachicSection
    Indicates a relationship where a subject is classified under, or associated with, a specific section or subdivision within halachic (Jewish legal) texts or rulings.
  • C. halakhicDebate
    Indicates a formal religious-legal dispute or discussion over the correct interpretation or application of Jewish law between parties.
  • D. halachicNote
    Indicates a relationship where one entity serves as a halachic (Jewish legal) note, comment, or annotation providing legal clarification or guidance about another entity.
  • E. halakhicApproach
    Indicates an entity’s method, stance, or interpretive framework for applying or understanding Jewish law (halakha) in practice.
  • 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_69e25d221d908190b9b502ad31e66a3f completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1c9887e5c819089437769acf684c4 completed April 29, 2026, 9:04 a.m.
PD Predicate disambiguation batch_69f1614612b481908c45d99e588882f9 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 8:11 p.m.