Triple
T35480442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhailo-Bhailo house-visiting tradition |
E1025455
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nepali festival tradition |
C54849
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Nepali festival tradition Context triple: [Bhailo-Bhailo house-visiting tradition, instanceOf, Nepali festival tradition]
-
A.
Nepali festival ritual
chosen
A Nepali festival ritual is a culturally significant, often religious ceremony involving prescribed actions, offerings, music, and communal gatherings that mark important seasonal, spiritual, or life-cycle events in Nepal.
-
B.
Newar festival
A Newar festival is a culturally rich, community-centered celebration of the Newar people of the Kathmandu Valley, combining elaborate rituals, processions, music, dance, and feasting to honor deities, ancestors, and seasonal cycles.
-
C.
Tibetan festival
A Tibetan festival is a culturally significant celebration in Tibet that combines religious rituals, traditional music and dance, colorful costumes, and communal gatherings to honor deities, mark seasonal changes, or commemorate historical events.
-
D.
Tihar tradition
Tihar tradition is a multi-day Hindu festival from Nepal and parts of India that honors humans, animals, and deities through rituals of light, worship, and familial celebration.
-
E.
Kashmiri Pandit festival
A Kashmiri Pandit festival is a traditional religious and cultural celebration observed by the Kashmiri Pandit community, marked by specific rituals, prayers, and customs rooted in Kashmiri Shaivism and local heritage.
- F. None of above.
Provenance (1 batch)
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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.