Triple
T33838896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diwali Festival of Lights (Auckland) |
E867307
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian cultural festival |
C45267
|
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: Indian cultural festival Context triple: [Diwali Festival of Lights (Auckland), instanceOf, Indian cultural festival]
-
A.
North Indian festival
A North Indian festival is a culturally significant celebration rooted in the traditions, religions, and seasonal cycles of northern India, typically marked by rituals, communal gatherings, music, dance, and regional cuisine.
-
B.
South Indian festival
A South Indian festival is a culturally significant celebration rooted in the traditions, religions, and seasonal cycles of South India, marked by region-specific rituals, cuisine, music, dance, and community gatherings.
-
C.
Indian national event
An Indian national event is a significant occasion officially recognized and celebrated across India to commemorate historical milestones, cultural heritage, or national achievements.
-
D.
Indo-Mauritian festival
An Indo-Mauritian festival is a cultural celebration in Mauritius rooted in Indian traditions, featuring religious rituals, music, dance, and communal gatherings that reflect the Indo-Mauritian community’s heritage and identity.
-
E.
Hindu religious event
chosen
A Hindu religious event is a ritualistic or celebratory gathering rooted in Hindu beliefs and traditions, typically involving worship, offerings, prayers, and cultural practices to honor deities, mark sacred times, or observe life-cycle ceremonies.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:47 a.m.