Triple
T11796452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afro-diasporic religions |
E280516
|
entity |
| Predicate | sharesDeityType |
P32474
|
FINISHED |
| Object | orishas |
—
|
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: orishas | Statement: [Afro-diasporic religions, sharesDeityType, orishas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesDeityType Context triple: [Afro-diasporic religions, sharesDeityType, orishas]
-
A.
sharesDeitiesWith
chosen
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
-
B.
deityCategory
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
C.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
D.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
E.
discussesDeity
Indicates that one entity talks or writes about, analyzes, or otherwise engages in discourse concerning a deity or divine being.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a1cda0819092d66a82fd882786 |
completed | April 10, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.