Triple
T10736439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seder Nashim |
E253206
|
entity |
| Predicate | positionInTalmud |
P95720
|
FINISHED |
| Object | third order |
—
|
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: third order | Statement: [Seder Nashim, positionInTalmud, third order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInTalmud Context triple: [Seder Nashim, positionInTalmud, third order]
-
A.
positionInTanakh
Indicates the relative location or ordering of a text or passage within the canonical structure of the Tanakh.
-
B.
positionInMishnehTorah
Indicates the specific location or ordering of a given item within the structure of the Mishneh Torah text.
-
C.
positionInMishnahOrders
Indicates the specific ordinal position that something occupies within the sequence of Mishnah orders.
-
D.
positionInHebrewBible
Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
-
E.
positionInAmidah
Indicates the specific location or order of a given element within the sequence of prayers that make up the Amidah.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71022aee0819091a5790d3dee6777 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:14 p.m.