Triple
T38504895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mato Oput |
E921737
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional reconciliation ceremony |
C57737
|
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: traditional reconciliation ceremony Context triple: [Mato Oput, instanceOf, traditional reconciliation ceremony]
-
A.
Native American ceremony
A Native American ceremony is a culturally significant ritual or gathering that expresses spiritual beliefs, honors ancestors and the natural world, and strengthens community bonds through traditional practices, songs, dances, and offerings.
-
B.
ceremonial tradition
chosen
A ceremonial tradition is a culturally established and repeatedly practiced set of formal actions, symbols, and rituals that mark significant events, express shared values, and reinforce group identity over time.
-
C.
ceremonial village
A ceremonial village is a community or settlement organized around shared ritual spaces and practices, where social, spiritual, and political life centers on recurring ceremonies and traditional gatherings.
-
D.
mediation ritual
A mediation ritual is a structured, often symbolic process through which a neutral third party facilitates communication and negotiation between conflicting parties to help them reach a mutually acceptable resolution.
-
E.
traditional council
A traditional council is a governing body composed of community elders or recognized leaders who make decisions, resolve disputes, and preserve cultural norms based on customary laws and practices.
- 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:32 p.m.