Triple
T2670473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yemoja |
E55733
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Yemọja |
E55733
|
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: Yemọja | Statement: [Yemoja, alsoKnownAs, Yemọja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yemọja Context triple: [Yemoja, alsoKnownAs, Yemọja]
-
A.
Yemoja
chosen
Yemoja is a major Yoruba water deity revered as a nurturing mother figure and protector associated with rivers, fertility, and the sea.
-
B.
Oshun
Oshun is a major Yoruba orisha revered as the goddess of fresh water, love, beauty, fertility, and diplomacy.
-
C.
Ifa
Ifa is a Yoruba divination and spiritual system centered on a complex corpus of sacred texts and the guidance of the deity Orunmila.
-
D.
Oyá
Oyá is a powerful Yoruba and Afro-Caribbean orisha associated with winds, storms, the cemetery, and transformative change.
-
E.
Ijesha
Ijesha are a subgroup of the Yoruba people known for their distinct dialect, cultural traditions, and historical presence in southwestern Nigeria.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd98d32ac8190b8edd9421b706532 |
completed | March 7, 2026, 7:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afa05f1ba48190a93a399d1067912c |
completed | March 10, 2026, 4:38 a.m. |
Created at: March 6, 2026, 9:54 p.m.