Triple
T23014513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arvit |
E572994
|
entity |
| Predicate | specialSeason |
P150680
|
FINISHED |
| Object | Selichot in some communities |
—
|
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: Selichot in some communities | Statement: [Arvit, specialSeason, Selichot in some communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialSeason Context triple: [Arvit, specialSeason, Selichot in some communities]
-
A.
promotionSeason
Indicates the specific season or time period during which a promotion or promotional campaign is active.
-
B.
seasonFeatured
Indicates that a particular season is highlighted, promoted, or given special prominence in relation to another entity (such as a series, platform, or collection).
-
C.
isHolidaySpecialOf
Indicates that something is a special version, event, or offering specifically created for or associated with a particular holiday.
-
D.
hasSeasonalHighlight
Indicates that something features a notable or emphasized aspect during a particular season or time of year.
-
E.
popularSeason
Indicates that a particular season is widely liked, favored, or frequently chosen by many people.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e3c0e08190a7ac747b056ec3ca |
completed | April 29, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:51 p.m.