Triple
T26704938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shona traditional religion |
E673262
|
entity |
| Predicate | biraPurpose |
P161141
|
FINISHED |
| Object | to call and consult ancestral spirits |
—
|
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: to call and consult ancestral spirits | Statement: [Shona traditional religion, biraPurpose, to call and consult ancestral spirits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biraPurpose Context triple: [Shona traditional religion, biraPurpose, to call and consult ancestral spirits]
-
A.
beerBrand
Indicates that one entity is a brand designation for a particular type or product of beer associated with the other entity.
-
B.
beerCulture
Indicates the presence, characteristics, or influence of traditions, practices, and social norms surrounding beer within a particular context or community.
-
C.
beerColor
Indicates the color characteristic associated with a particular beer.
-
D.
beerStyle
Indicates that one entity is the style or type classification of a beer associated with another entity.
-
E.
breweryType
Indicates the specific category or classification of a brewery based on its operational or business characteristics.
- F. None of above. chosen
Provenance (4 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f617b8e61881909eef2e8eaf1bc969 |
completed | May 2, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 3:33 a.m.