Triple
T5339231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galungan |
E123903
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Balinese Hindu festival |
C2504
|
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: Balinese Hindu festival Context triple: [Galungan, instanceOf, Balinese Hindu festival]
-
A.
Javanese historical event
A Javanese historical event is a significant occurrence in the past that took place in Java or involved Javanese people, shaping the island’s political, social, cultural, or religious development.
-
B.
religious festival
chosen
A religious festival is a recurring, community-based celebration rooted in spiritual beliefs and traditions, marked by rituals, ceremonies, and social gatherings that honor deities, sacred events, or religious values.
-
C.
Islamic religious festival
An Islamic religious festival is a recurring sacred occasion in Islam, marked by specific rituals, communal worship, and cultural practices that commemorate key events in Islamic belief and history.
-
D.
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.
-
E.
Greek religious festival
A Greek religious festival is a recurring communal celebration in ancient Greek society that combines ritual worship of specific deities with processions, sacrifices, athletic or artistic competitions, and feasting to honor the gods and reinforce civic and religious identity.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2 p.m.