Triple
T25375710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bribri traditional religion |
E633050
|
entity |
| Predicate | hasReligiousSpecialistRole |
P143890
|
FINISHED |
| Object | awa |
—
|
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: awa | Statement: [Bribri traditional religion, hasReligiousSpecialistRole, awa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousSpecialistRole Context triple: [Bribri traditional religion, hasReligiousSpecialistRole, awa]
-
A.
hasReligiousRoleEquivalent
Indicates that two religious roles are considered functionally or hierarchically equivalent within or across religious traditions.
-
B.
hasReligiousOffice
Indicates that an entity holds or occupies a specific religious role, position, or office within a religious organization or tradition.
-
C.
hasClergyType
Indicates the specific category or role of clergy associated with an entity.
-
D.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
E.
religiousAndSpiritualRole
chosen
Indicates that an entity holds or fulfills a religious or spiritual function, office, or responsibility in relation to another entity or context.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 21, 2026, 1:38 p.m.