Triple

T14717872
Position Surface form Disambiguated ID Type / Status
Subject Bini people E345730 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: [Bini people, traditionalDeity, Osanobua]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Osanobua
Context triple: [Bini people, 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. Osubi
    Osubi is a town in Delta State, Nigeria, known for hosting a regional airport that serves the nearby city of Warri and surrounding communities.
  • C. Yasu
    Yasu is a Japanese city located in Shiga Prefecture, known for its blend of residential areas, local industry, and proximity to Lake Biwa.
  • D. Michitaka
    Michitaka is a Japanese given name that has been borne by various historical and contemporary figures.
  • E. Shinshiro
    Shinshiro is a city in eastern Aichi Prefecture, Japan, known for its mountainous scenery, historic battle sites, and traditional rural landscapes.
  • 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_69d822e5911c8190ba589f957dbd9ba7 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb98688f48190b2b19ce7aa06a6db completed April 14, 2026, 10:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffcf0743288190b3bec8c48b5c7893 completed May 10, 2026, 12:19 a.m.
Created at: April 10, 2026, 1:29 a.m.