Triple
T37296593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiwa people |
E925820
|
entity |
| Predicate | spiritualLeaders |
P35921
|
FINISHED |
| Object | mamos |
—
|
NE NERFINISHED |
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: mamos | Statement: [Wiwa people, spiritualLeaders, mamos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spiritualLeaders Context triple: [Wiwa people, spiritualLeaders, mamos]
-
A.
spiritualLeaderOf
chosen
Indicates that one entity serves as the primary religious or spiritual guide, authority, or mentor for another entity or group.
-
B.
spiritualDirector
Indicates a relationship where one entity serves as a spiritual guide, mentor, or counselor to another in matters of faith and personal spiritual growth.
-
C.
politicalAndSpiritualLeaderHistorically
Indicates that an entity has historically held both political authority and spiritual or religious leadership over others.
-
D.
religiousLeadershipStart
Indicates the point in time when an entity begins serving in a religious leadership role or office.
-
E.
religiousLeadershipSupport
Indicates that one entity provides backing, endorsement, or assistance to another in the context of religious leadership or authority.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.