Triple
T34085340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sawan |
E874162
|
entity |
| Predicate | hasSpecialObservance |
P44757
|
FINISHED |
| Object | Sawan Somvar fasts |
—
|
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: Sawan Somvar fasts | Statement: [Sawan, hasSpecialObservance, Sawan Somvar fasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialObservance Context triple: [Sawan, hasSpecialObservance, Sawan Somvar fasts]
-
A.
hasFeastOrCommemoration
chosen
Indicates that a particular day, event, or context includes an associated religious feast, liturgical celebration, or commemorative observance.
-
B.
includesSpecialDay
Indicates that a time period, schedule, or collection contains or encompasses at least one designated special day or occasion.
-
C.
observesHolidayWithLocalCustoms
Indicates that an entity celebrates a holiday in a particular place following that location’s specific traditions and customs.
-
D.
mayObserveHoliday
Indicates that an entity is permitted or allowed to observe or celebrate a particular holiday.
-
E.
feastDayObservedOn
Indicates that a particular feast day is celebrated or formally observed on a specified calendar date.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 1, 2026, 1:52 a.m.