Triple
T2583676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ife Kingdom |
E57148
|
entity |
| Predicate | hasMythicStatus |
P24829
|
FINISHED |
| Object | navel of the world in Yoruba cosmology |
—
|
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: navel of the world in Yoruba cosmology | Statement: [Ife Kingdom, hasMythicStatus, navel of the world in Yoruba cosmology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythicStatus Context triple: [Ife Kingdom, hasMythicStatus, navel of the world in Yoruba cosmology]
-
A.
hasMythicMotif
Indicates that one entity features, embodies, or is associated with a particular mythic motif found in the other entity.
-
B.
hasMythicTheme
Indicates that something embodies, references, or is characterized by a mythic or mythological theme.
-
C.
hasMythType
Indicates that an entity is associated with or classified under a particular type or category of myth.
-
D.
mythicReputation
chosen
Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
-
E.
hasMythSource
Indicates that something derives from, is based on, or is supported by a particular myth or mythological source.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3cb33a08190a3eae1a95e1b63bf |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.