Triple
T18889477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challah |
E462043
|
entity |
| Predicate | hasSpecialFormForHoliday |
P17592
|
FINISHED |
| Object | round challah for Rosh Hashanah |
—
|
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: round challah for Rosh Hashanah | Statement: [Challah, hasSpecialFormForHoliday, round challah for Rosh Hashanah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialFormForHoliday Context triple: [Challah, hasSpecialFormForHoliday, round challah for Rosh Hashanah]
-
A.
includesSpecialDay
Indicates that a time period, schedule, or collection contains or encompasses at least one designated special day or occasion.
-
B.
hasHolidayCustom
chosen
Indicates that there is a specific traditional practice or custom associated with a particular holiday.
-
C.
hasCommonHoliday
Indicates that two entities share at least one holiday that is observed or celebrated in common.
-
D.
isHolidaySpecialOf
Indicates that something is a special version, event, or offering specifically created for or associated with a particular holiday.
-
E.
hasMunicipalHoliday
Indicates that a particular place or jurisdiction observes a specific municipal holiday as part of its official local 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c479f3208190a9d665865c4b630b |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.