Triple
T11579886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Candomblé |
E274597
|
entity |
| Predicate | centralDeities |
P85058
|
FINISHED |
| Object | orixás |
—
|
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: orixás | Statement: [Candomblé, centralDeities, orixás]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralDeities Context triple: [Candomblé, centralDeities, orixás]
-
A.
mainDeity
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
-
B.
deityCategory
chosen
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
C.
otherDeity
Indicates that one deity is distinct from and not identical to another deity within a given context or system.
-
D.
sharesDeitiesWith
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
-
E.
hasNumberOfDeities
Indicates the specific count of deities associated with an entity, such as a religion, mythology, or belief system.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8904b46288190890ecafd6ceb0c3d |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.