Triple

T13611691
Position Surface form Disambiguated ID Type / Status
Subject Opa Oranmiyan E325203 entity
Predicate associatedWith P37 FINISHED
Object Oranmiyan E1047695 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: Oranmiyan | Statement: [Opa Oranmiyan, associatedWith, Oranmiyan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oranmiyan
Context triple: [Opa Oranmiyan, associatedWith, Oranmiyan]
  • A. Oranmiyan chosen
    Oranmiyan is a legendary Yoruba prince and warrior-king regarded as a founding figure of both the Oyo Empire in present-day Nigeria and the Benin Kingdom.
  • B. Orile
    Orile is a residential and commercial neighborhood located within the Surulere area of Lagos, Nigeria.
  • C. Ojota
    Ojota is a busy Lagos suburb and transport hub known for its major bus terminal and strategic location along key routes in the city.
  • D. Ewulu
    Ewulu is a town in Aniocha South Local Government Area of Delta State, Nigeria, known as one of the Igbo communities in the region.
  • E. Ikwerre
    Ikwerre is a Niger-Congo language spoken primarily by the Ikwerre people in Rivers State, Nigeria, particularly in and around Port Harcourt.
  • 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_69d8076aae28819092cf636190ee5529 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb0aa9a1481908c6f92495aff86c6 completed April 12, 2026, 2:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7942e8c9c8190ab843cc4c31f512a completed May 3, 2026, 6:30 p.m.
Created at: April 9, 2026, 9:50 p.m.