Triple
T37652207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omoloko |
E937202
|
entity |
| Predicate | recognizesSpiritCategory |
P105130
|
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: [Omoloko, recognizesSpiritCategory, orixás]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesSpiritCategory Context triple: [Omoloko, recognizesSpiritCategory, orixás]
-
A.
recognizesSpirit
Indicates that one entity acknowledges, identifies, or affirms the spiritual nature, presence, or authority of another entity.
-
B.
associatedSpiritCategory
chosen
Indicates that one entity is linked to another as the category or type under which a particular spirit or spiritual being is classified.
-
C.
typeOfSpirit
Indicates the specific kind or category of spirit (e.g., ghost, demon, angel) that an entity belongs to.
-
D.
hasSpiritSymbolRole
Indicates that an entity serves in a designated role or function specifically associated with a spirit symbol.
-
E.
baseSpiritType
Indicates the type or category of the primary alcoholic spirit that serves as the base in a drink or spirit product.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 3, 2026, 4:18 p.m.