Triple
T2571569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regla de Ocha |
E57674
|
entity |
| Predicate | hasImportantDeity |
P7648
|
FINISHED |
| Object | Oshún |
E58293
|
NE 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: Oshún | Statement: [Regla de Ocha, hasImportantDeity, Oshún]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oshún Context triple: [Regla de Ocha, hasImportantDeity, Oshún]
-
A.
Oshun
chosen
Oshun is a major Yoruba orisha revered as the goddess of fresh water, love, beauty, fertility, and diplomacy.
-
B.
Yemoja
Yemoja is a major Yoruba water deity revered as a nurturing mother figure and protector associated with rivers, fertility, and the sea.
-
C.
Ogun
Ogun is a major Yoruba deity revered as the god of iron, war, and craftsmanship, often associated with metalworking, technology, and the clearing of paths.
-
D.
Shango
Shango is a major Yoruba orisha revered as the powerful god of thunder, lightning, and justice, often associated with kingship and drumming.
-
E.
Nanna
Nanna is the Sumerian moon god, a major deity associated with wisdom, fertility, and the measurement of time.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd8317b0481908d6d1436732253b2 |
completed | March 7, 2026, 7:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af83aefb00819095a6ab26f9bb61d9 |
completed | March 10, 2026, 2:36 a.m. |
Created at: March 6, 2026, 9:48 p.m.