Triple
T13376856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savoraim |
E319208
|
entity |
| Predicate | chronologicalPositionInRabbinicEras |
P10549
|
FINISHED |
| Object | between Amoraim and Geonim |
—
|
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: between Amoraim and Geonim | Statement: [Savoraim, chronologicalPositionInRabbinicEras, between Amoraim and Geonim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalPositionInRabbinicEras Context triple: [Savoraim, chronologicalPositionInRabbinicEras, between Amoraim and Geonim]
-
A.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
B.
positionInHebrewCalendar
Indicates the specific placement or ordering of a time point (such as a date or event) within the structure of the Hebrew calendar.
-
C.
timeframeRelativeToRoshHashanah
Indicates the temporal relationship of an event or period in reference to Rosh Hashanah (e.g., before, during, or after the holiday).
-
D.
positionInEra
chosen
Indicates the temporal placement or role of something within a specific historical or chronological era.
-
E.
טווח בלוח הגרגוריאני
Indicates a temporal relationship where something occurs, is valid, or is defined within a specified date range on the Gregorian calendar.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce3fec48190a5443d87c85477a3 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:33 p.m.