Triple

T4664057
Position Surface form Disambiguated ID Type / Status
Subject Sifra E102801 entity
Predicate inHalakhicCategory P17761 FINISHED
Object Torah-based law exegesis 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: Torah-based law exegesis | Statement: [Sifra, inHalakhicCategory, Torah-based law exegesis]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inHalakhicCategory
Context triple: [Sifra, inHalakhicCategory, Torah-based law exegesis]
  • A. halachicCategory chosen
    Indicates the classification of something according to Jewish legal (halachic) categories or rulings.
  • B. halakhicStatus
    Indicates the formal standing or classification of an entity according to Jewish law (halakha), especially in terms of what is religiously permitted, required, or prohibited.
  • C. 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.
  • D. halakhicPrinciple
    Indicates a relationship where a rule, decision, or action is governed or justified by a specific principle of Jewish religious law (halakha).
  • 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_69bd43d9cba4819086c1ab1c2d9d2133 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd633aeba88190a8329ed022d685b6 completed March 20, 2026, 3:09 p.m.
PD Predicate disambiguation batch_69bd62126b0c81909ba3f21b21e30d54 completed March 20, 2026, 3:04 p.m.
Created at: March 20, 2026, 1:15 p.m.