Triple

T34424167
Position Surface form Disambiguated ID Type / Status
Subject Tractate Shabbat E883624 entity
Predicate hasSection P35 FINISHED
Object Perek HaBoneh
Perek HaBoneh is a chapter within the Talmudic tractate Shabbat that focuses on the laws and prohibitions related to building and construction on the Sabbath.
E2099476 NE 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: Perek HaBoneh | Statement: [Tractate Shabbat, hasSection, Perek HaBoneh]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Perek HaBoneh
Triple: [Tractate Shabbat, hasSection, Perek HaBoneh]
Generated description
Perek HaBoneh is a chapter within the Talmudic tractate Shabbat that focuses on the laws and prohibitions related to building and construction on the Sabbath.

Provenance (5 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_69f349c3dd2c819092cc9e64809f4a42 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f718de4b9c819096e9abb14ed149e5 completed May 3, 2026, 9:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a372123af5481909dbe0614de5537aa completed June 20, 2026, 11:24 p.m.
NEDg Description generation batch_6a372519bb4c8190aa8389c6138094a2 completed June 20, 2026, 11:41 p.m.
NED2 Entity disambiguation (via description) batch_6a37257e91488190a32fbfb85bb1ce1d completed June 20, 2026, 11:42 p.m.
Created at: May 1, 2026, 2 a.m.