Triple

T7206686
Position Surface form Disambiguated ID Type / Status
Subject Cup’ig E148682 entity
Predicate hasCeremonialTradition P19423 FINISHED
Object dance ceremonies 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: dance ceremonies | Statement: [Cup’ig, hasCeremonialTradition, dance ceremonies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCeremonialTradition
Context triple: [Cup’ig, hasCeremonialTradition, dance ceremonies]
  • A. ceremonialOrigin
    Indicates that something originates from, or is derived through, a formal ceremony or ritual practice.
  • B. establishedTradition
    Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
  • C. ceremonialUse
    Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
  • D. hasTraditionIn chosen
    Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
  • E. haveCeremonialHead
    Indicates that one entity serves as the formal or symbolic head or leader of another entity, typically without holding full executive power.
  • 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_69c687e8cf188190b5f3ecffd681f04e completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6e969c5fc819096bc03bfba12d0cf completed March 27, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69c6e757fed4819091b0a096e3befc3a completed March 27, 2026, 8:23 p.m.
Created at: March 27, 2026, 2:52 p.m.