Triple
T2998688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purim Katan |
E81132
|
entity |
| Predicate | hasObligationOfFestiveMeal |
P44942
|
FINISHED |
| Object | disputed |
—
|
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: disputed | Statement: [Purim Katan, hasObligationOfFestiveMeal, disputed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObligationOfFestiveMeal Context triple: [Purim Katan, hasObligationOfFestiveMeal, disputed]
-
A.
hasAssociatedFeast
Indicates that something (such as a person, event, or entity) is linked to a specific feast or celebratory religious observance.
-
B.
isFixedFeast
Indicates that an event or celebration occurs on the same calendar date every year, rather than moving relative to other dates.
-
C.
eatenOnOccasion
Indicates that one entity is consumed or eaten by another only at certain times or under specific circumstances, rather than regularly or habitually.
-
D.
containsFixedFeasts
Indicates that an entity includes or encompasses specific feasts that occur on fixed, recurring calendar dates.
-
E.
hasSpecialMeal
Indicates that an entity provides, is assigned, or is associated with a designated special meal option.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f766408190a5591efce8346bb9 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 2:59 p.m.