Triple
T11147178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinnim |
E263697
|
entity |
| Predicate | orderInSederKodashim |
P37923
|
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: [Kinnim, orderInSederKodashim, last tractate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderInSederKodashim Context triple: [Kinnim, orderInSederKodashim, 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.
positionInMishnahOrders
chosen
Indicates the specific ordinal position that something occupies within the sequence of Mishnah orders.
-
C.
traditionalJewishOrder
Indicates that something follows or conforms to the customary or historically established order used in Jewish tradition.
-
D.
halachicSection
Indicates a relationship where a subject is classified under, or associated with, a specific section or subdivision within halachic (Jewish legal) texts or rulings.
-
E.
positionInMishnehTorah
Indicates the specific location or ordering of a given item within the structure of the Mishneh Torah text.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e86e9ef48190b4df4b14319a954f |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.