Triple
T36821917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oohenumpa Lakota |
E909907
|
entity |
| Predicate | usesSacredPractice |
P124620
|
FINISHED |
| Object | sweat lodge ceremony |
—
|
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: sweat lodge ceremony | Statement: [Oohenumpa Lakota, usesSacredPractice, sweat lodge ceremony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSacredPractice Context triple: [Oohenumpa Lakota, usesSacredPractice, sweat lodge ceremony]
-
A.
usesSacredArtForm
Indicates that one entity employs or incorporates a sacred or religiously significant art form in relation to another entity or context.
-
B.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
C.
sacredElement
Indicates that one entity is regarded as holy, revered, or spiritually significant within the religious or cultural context of the other entity.
-
D.
usesRitually
chosen
Indicates that an entity employs or performs something as part of a ritual or ceremonial practice.
-
E.
usesSacredSpace
Indicates that an entity makes use of a designated sacred or holy space for its activities or purposes.
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: May 3, 2026, 4:13 p.m.