Triple
T12272176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edo (Bini) |
E292497
|
entity |
| Predicate | traditionalDeity |
P5606
|
FINISHED |
| Object | Osanobua |
E941366
|
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: Osanobua | Statement: [Edo (Bini), traditionalDeity, Osanobua]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Osanobua Context triple: [Edo (Bini), traditionalDeity, Osanobua]
-
A.
Osanobua
chosen
Osanobua is the supreme creator god and central deity in the traditional religion and cosmology of the Edo people of Nigeria.
-
B.
Yasu
Yasu is a Japanese city located in Shiga Prefecture, known for its blend of residential areas, local industry, and proximity to Lake Biwa.
-
C.
Michitaka
Michitaka is a Japanese given name that has been borne by various historical and contemporary figures.
-
D.
Shinshiro
Shinshiro is a city in eastern Aichi Prefecture, Japan, known for its mountainous scenery, historic battle sites, and traditional rural landscapes.
-
E.
Takayoshi
Takayoshi is a Japanese given name notably borne by Kido Takayoshi, a key samurai and statesman of the Meiji Restoration.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cee7158819093fff74db6867896 |
completed | April 10, 2026, 3:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e6981b48190a0fc5a571c425be1 |
completed | May 2, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:52 p.m.