Triple
T34572391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uktzin |
E887658
|
entity |
| Predicate | positionInMishnahOrder |
P37923
|
FINISHED |
| Object | final 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: final tractate | Statement: [Uktzin, positionInMishnahOrder, final tractate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInMishnahOrder Context triple: [Uktzin, positionInMishnahOrder, final tractate]
-
A.
positionInMishnahOrders
chosen
Indicates the specific ordinal position that something occupies within the sequence of Mishnah orders.
-
B.
positionInMishnehTorah
Indicates the specific location or ordering of a given item within the structure of the Mishneh Torah text.
-
C.
positionInTalmud
Indicates the specific location or ordering of a passage, topic, or element within the structured text of the Talmud.
-
D.
positionInHebrewBible
Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
-
E.
positionInTanakh
Indicates the relative location or ordering of a text or passage within the canonical structure of the Tanakh.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff6a4ce9a08190b98abde3a170dd69 |
completed | May 9, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69ff69c11634819089d1084bd2c11534 |
completed | May 9, 2026, 5:07 p.m. |
Created at: May 1, 2026, 2:03 a.m.