Triple
T21561856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosh Hashanah LaIlanot |
E532055
|
entity |
| Predicate | fixedOnHebrewDate |
P34725
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rosh Hashanah LaIlanot, fixedOnHebrewDate, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fixedOnHebrewDate Context triple: [Rosh Hashanah LaIlanot, fixedOnHebrewDate, true]
-
A.
positionInHebrewCalendar
Indicates the specific placement or ordering of a time point (such as a date or event) within the structure of the Hebrew calendar.
-
B.
dateInHebrewCalendar
Indicates that a specific date is expressed according to the Hebrew (Jewish) calendar system rather than another calendar.
-
C.
isFixedFeast
chosen
Indicates that an event or celebration occurs on the same calendar date every year, rather than moving relative to other dates.
-
D.
timeframeRelativeToRoshHashanah
Indicates the temporal relationship of an event or period in reference to Rosh Hashanah (e.g., before, during, or after the holiday).
-
E.
linkedToJewishHoliday
Indicates that something has a direct association or connection with a specific Jewish holiday.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e3e2348190b5c3b66cdc871e6e |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.