Triple
T25422598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boduberu dance |
E637022
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maldivian cultural practice |
C10380
|
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: Maldivian cultural practice Context triple: [Boduberu dance, instanceOf, Maldivian cultural practice]
-
A.
Cultural practice
chosen
A cultural practice is a shared, patterned activity or behavior through which a group expresses, maintains, and transmits its values, beliefs, and social norms.
-
B.
Balinese Hindu observance
A Balinese Hindu observance is a culturally specific religious practice or ritual in Bali that harmonizes Hindu theology with local customs, ancestral traditions, and cyclical ceremonies to maintain balance between the spiritual and earthly realms.
-
C.
Maldivian language
The Maldivian language, also known as Dhivehi, is an Indo-Aryan language spoken primarily in the Maldives, characterized by its unique Thaana script and influences from Arabic, Sinhalese, and Dravidian languages.
-
D.
Ryukyuan cultural heritage
Ryukyuan cultural heritage encompasses the traditional customs, languages, arts, beliefs, and historical practices of the indigenous Ryukyuan peoples of Okinawa and the surrounding Ryukyu Islands, shaped by centuries of interaction with Japan, China, and Southeast Asia.
-
E.
Balinese polity
A Balinese polity is a traditional socio-political entity in Bali characterized by a hierarchical kingship, ritual authority, and complex relationships between royal courts, villages, and religious institutions.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 1:57 p.m.