Triple

T36250107
Position Surface form Disambiguated ID Type / Status
Subject Tractate Taanit E891775 entity
Predicate hasVersion P455 FINISHED
Object Mishnah Taanit
Mishnah Taanit is the section of the Mishnah that outlines Jewish laws and practices related to public fasts, prayer for rain, and communal responses to drought and calamity.
E891775 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: Mishnah Taanit | Statement: [Tractate Taanit, hasVersion, Mishnah Taanit]
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: Mishnah Taanit
Triple: [Tractate Taanit, hasVersion, Mishnah Taanit]
Generated description
Mishnah Taanit is the section of the Mishnah that outlines Jewish laws and practices related to public fasts, prayer for rain, and communal responses to drought and calamity.

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_69f76e4599108190811532e707d6bc2c completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b5f9a88c819089c3f1e355b45f15 completed May 3, 2026, 8:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a394d4a5bac8190954461bb396e1289 completed June 22, 2026, 2:57 p.m.
NEDg Description generation batch_6a394f0c50f88190a119bae5ad7af076 completed June 22, 2026, 3:04 p.m.
NED2 Entity disambiguation (via description) batch_6a39514c8b688190be3f7f8b911d0b35 completed June 22, 2026, 3:14 p.m.
Created at: May 3, 2026, 4:09 p.m.