Triple
T37569042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omolu |
E934637
|
entity |
| Predicate | associatedOrisha |
P175994
|
FINISHED |
| Object | Nanã |
E934638
|
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: Nanã | Statement: [Omolu, associatedOrisha, Nanã]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedOrisha Context triple: [Omolu, associatedOrisha, Nanã]
-
A.
associatedDeityOrForce
Indicates that one entity is linked to, represented by, or under the influence of a particular deity or supernatural force.
-
B.
closelyAssociatedDeity
chosen
Indicates a deity that is strongly connected or frequently linked to another entity, such as a person, place, object, or concept, through special association or significance.
-
C.
associatedGoddess
Indicates that one entity is recognized as the goddess traditionally linked or connected to another entity (such as a place, concept, or deity).
-
D.
orientationOfDeity
Indicates the directional or positional alignment associated with a deity in relation to a reference point or context.
-
E.
associatedSpirit
Indicates a relationship where one entity is linked to or accompanied by a particular spirit, often as a guide, protector, or defining supernatural presence.
- F. None of above.
Provenance (4 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a409f1c5d04819090aec6f3ddb5a8ac |
completed | June 28, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.