Triple
T35315694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barasana people |
E1019897
|
entity |
| Predicate | shamanism |
P155046
|
FINISHED |
| Object | important religious role |
—
|
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: important religious role | Statement: [Barasana people, shamanism, important religious role]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shamanism Context triple: [Barasana people, shamanism, important religious role]
-
A.
ritualSpecialist
Indicates that one entity serves as a designated expert or practitioner responsible for performing or overseeing rituals in relation to another entity or context.
-
B.
hasShamans
chosen
Indicates that an entity possesses, employs, or is associated with one or more shamans.
-
C.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
D.
sacredRiverCult
Indicates a religious practice or belief system that venerates a river as sacred and centers rituals, worship, or cultic activities around it.
-
E.
primarySpirit
Indicates that one entity is the main or most fundamental spiritual essence associated with another entity.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f790918e2481908851ef7fa47f9d19 |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.