Triple
T4839000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lag BaOmer |
E108132
|
entity |
| Predicate | occursOnHebrewDate |
P11560
|
FINISHED |
| Object | 18 Iyar |
—
|
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: 18 Iyar | Statement: [Lag BaOmer, occursOnHebrewDate, 18 Iyar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursOnHebrewDate Context triple: [Lag BaOmer, occursOnHebrewDate, 18 Iyar]
-
A.
dateInHebrewCalendar
chosen
Indicates that a specific date is expressed according to the Hebrew (Jewish) calendar system rather than another calendar.
-
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.
linkedToJewishHoliday
Indicates that something has a direct association or connection with a specific Jewish holiday.
-
E.
monthInHebrewCalendar
Indicates that one entity is a specific month as defined in the Hebrew calendar system in relation to another entity.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2375a4819098e16acb982c8fab |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.