Triple
T2583604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shango |
E57147
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Oshun |
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: Oshun | Statement: [Shango, spouse, Oshun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oshun Context triple: [Shango, spouse, Oshun]
-
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.
Chalchiuhtlicue
Chalchiuhtlicue is an Aztec goddess associated with water, rivers, lakes, and childbirth, often depicted as a protector of women and children.
-
D.
Atargatis
Atargatis is an ancient Syrian mother and fertility goddess often associated with water, fish, and protection, and widely worshipped across the Near East.
-
E.
Inanna
Inanna is the ancient Mesopotamian goddess of love, beauty, sex, war, and political power, later known as Ishtar.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3cb33a08190a3eae1a95e1b63bf |
completed | March 7, 2026, 7:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af907510d481909e7c5e5207d17774 |
completed | March 10, 2026, 3:31 a.m. |
Created at: March 6, 2026, 9:49 p.m.