Triple
T34424409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiddushin |
E883629
|
entity |
| Predicate | orderWithinSederNashim |
P181477
|
FINISHED |
| Object | last tractate |
—
|
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: last tractate | Statement: [Kiddushin, orderWithinSederNashim, last tractate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderWithinSederNashim Context triple: [Kiddushin, orderWithinSederNashim, last tractate]
-
A.
sectionOfShulchanAruch
Indicates that one entity is a specific section or part within the larger halachic work known as the Shulchan Aruch.
-
B.
firstSederNight
Indicates that the relationship or event occurs on the first night of the Passover Seder.
-
C.
relationshipToShulchanAruch
Indicates the nature or type of connection that something has to the Shulchan Aruch, such as dependence on, conformity with, or derivation from it.
-
D.
secondSederNight
Indicates that the relationship or event occurs on the second night of the Passover Seder.
-
E.
genderOfMitzvah
Indicates the gender category associated with performing or being obligated in a particular mitzvah (commandment).
- F. None of above. chosen
Provenance (4 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_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69f77648979c8190b6cdbb835ab8987c |
completed | May 3, 2026, 4:22 p.m. |
Created at: May 1, 2026, 2 a.m.