Triple

T7011465
Position Surface form Disambiguated ID Type / Status
Subject Central Sumba Regency E162590 entity
Predicate hasTraditionalFestivals P19423 FINISHED
Object Marapu rituals 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: Marapu rituals | Statement: [Central Sumba Regency, hasTraditionalFestivals, Marapu rituals]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTraditionalFestivals
Context triple: [Central Sumba Regency, hasTraditionalFestivals, Marapu rituals]
  • A. hasCulturalEvent
    Indicates that a cultural event (such as a festival, performance, or exhibition) takes place in, is associated with, or is hosted by a given entity.
  • B. hasFestival
    Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
  • C. hasTraditionIn chosen
    Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
  • D. hasParades
    Indicates that an entity regularly holds or hosts parades as events or activities.
  • E. hasFestivalImportance
    Indicates that something holds notable significance, relevance, or prominence within the context of a festival or festive event.
  • 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_69c6885a127c8190867b059bdccf13ff completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dc5729448190af66dbd6f3e8936e completed March 27, 2026, 7:36 p.m.
PD Predicate disambiguation batch_69c6d7c790288190b7cbbaa4a5f9c91d completed March 27, 2026, 7:17 p.m.
Created at: March 27, 2026, 2:34 p.m.