Triple

T23728132
Position Surface form Disambiguated ID Type / Status
Subject Sefer shel Beinonim E586335 entity
Predicate statusInChabad P21335 FINISHED
Object considered the core of Tanya 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: considered the core of Tanya | Statement: [Sefer shel Beinonim, statusInChabad, considered the core of Tanya]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: statusInChabad
Context triple: [Sefer shel Beinonim, statusInChabad, considered the core of Tanya]
  • A. statusInRabbinicLiterature
    Indicates how a person, concept, or text is regarded, classified, or treated within rabbinic literature and tradition.
  • B. viewedByChabadAs chosen
    Indicates how something or someone is regarded, interpreted, or characterized specifically within Chabad’s perspective or doctrinal viewpoint.
  • C. timeAsChabadCenter
    Indicates that a location functioned as a Chabad center during a specified period of time.
  • D. orthodoxStatus
    Indicates that an entity conforms to, aligns with, or is recognized as following an established or traditional set of doctrines, beliefs, or practices.
  • E. 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.
  • 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_69e24907dc9c8190be074c9c96a0ec2d completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b91740ac81908ca99de0c56f6b57 completed April 29, 2026, 7:53 a.m.
PD Predicate disambiguation batch_69f155e4b1148190836ede4741dcb888 completed April 29, 2026, 12:50 a.m.
Created at: April 17, 2026, 7:09 p.m.