Triple
T34424367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gittin |
E883628
|
entity |
| Predicate | traditionalOrderInNashim |
P181477
|
FINISHED |
| Object | fifth |
—
|
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: fifth | Statement: [Gittin, traditionalOrderInNashim, fifth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalOrderInNashim Context triple: [Gittin, traditionalOrderInNashim, fifth]
-
A.
traditionalOrder
Indicates that entities are arranged or occur according to a customary, historically established sequence or hierarchy.
-
B.
orderWithinSederNashim
chosen
Indicates the relative position or sequence of an item within the tractates of Seder Nashim in the Mishnah/Talmud ordering.
-
C.
traditionalJewishOrder
Indicates that something follows or conforms to the customary or historically established order used in Jewish tradition.
-
D.
normalOrder
Indicates that the entities are arranged or occur in their standard, default, or expected sequence.
-
E.
orderInSederMoed
Indicates the sequential position that an item occupies within the Seder Moed order.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 1, 2026, 2 a.m.