Triple
T11147147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middot |
E263696
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object |
tractate Tamid
Tractate Tamid is a section of the Mishnah and Talmud that details the daily sacrificial service and routine of the priests in the Jerusalem Temple.
|
E47695
|
NE FINISHED |
How this triple was built (4 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: tractate Tamid | Statement: [Middot, relatedTo, tractate Tamid]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: tractate Tamid Context triple: [Middot, relatedTo, tractate Tamid]
-
A.
Arba’ah Turim
Arba’ah Turim is a foundational 14th-century Jewish legal code by Rabbi Jacob ben Asher that systematically organizes and clarifies halakhic rulings for practical religious life.
-
B.
Taslḥit
Taslḥit is a variety of the Amazigh (Berber) language spoken primarily in southwestern Morocco.
-
C.
Tohorot
Tohorot is a tractate of the Mishnah that deals with the complex laws of ritual purity and impurity.
-
D.
Makkot
Makkot is a Talmudic tractate in the order of Nezikin that primarily deals with judicial punishments such as lashes, false witnesses, and cities of refuge.
-
E.
Kodashim
Kodashim is the order of the Mishnah that deals with sacrificial rites, Temple service, and other holy offerings and sancta in Jewish law.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: tractate Tamid Triple: [Middot, relatedTo, tractate Tamid]
Generated description
Tractate Tamid is a section of the Mishnah and Talmud that details the daily sacrificial service and routine of the priests in the Jerusalem Temple.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: tractate Tamid Target entity description: Tractate Tamid is a section of the Mishnah and Talmud that details the daily sacrificial service and routine of the priests in the Jerusalem Temple.
-
A.
Arba’ah Turim
Arba’ah Turim is a foundational 14th-century Jewish legal code by Rabbi Jacob ben Asher that systematically organizes and clarifies halakhic rulings for practical religious life.
-
B.
Taslḥit
Taslḥit is a variety of the Amazigh (Berber) language spoken primarily in southwestern Morocco.
-
C.
Tohorot
Tohorot is a tractate of the Mishnah that deals with the complex laws of ritual purity and impurity.
-
D.
Makkot
Makkot is a Talmudic tractate in the order of Nezikin that primarily deals with judicial punishments such as lashes, false witnesses, and cities of refuge.
-
E.
Kodashim
chosen
Kodashim is the order of the Mishnah that deals with sacrificial rites, Temple service, and other holy offerings and sancta in Jewish law.
- F. None of above.
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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e86e9ef48190b4df4b14319a954f |
completed | April 9, 2026, 5:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e442248e588190b59866c79169c43a |
completed | April 19, 2026, 2:47 a.m. |
| NEDg | Description generation | batch_69e44c0a9edc8190a184244ba63f1c8f |
completed | April 19, 2026, 3:29 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69e4513731fc8190be0bae62d1e16e6f |
completed | April 19, 2026, 3:51 a.m. |
Created at: April 8, 2026, 9:28 p.m.