Triple

T11580312
Position Surface form Disambiguated ID Type / Status
Subject New Oyo E274608 entity
Predicate alsoKnownAs P39 FINISHED
Object Oyo E56234 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: Oyo | Statement: [New Oyo, alsoKnownAs, Oyo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oyo
Context triple: [New Oyo, alsoKnownAs, Oyo]
  • A. Oyo chosen
    Oyo is a prominent Yoruba subgroup historically known for its powerful Oyo Empire in what is now southwestern Nigeria.
  • B. Oyo State
    Oyo State is a southwestern Nigerian state historically known as the heartland of the old Oyo Empire and a major center of Yoruba culture and politics.
  • C. Oyo-Ile
    Oyo-Ile was the historic political and cultural center of the Oyo Empire, one of the most powerful precolonial Yoruba states in West Africa.
  • D. Tangambalanga
    Tangambalanga is a small rural township in northeastern Victoria, Australia, known for its dairy industry and proximity to the regional city of Wodonga.
  • E. Chuda State
    Chuda State was a former princely state in western India historically associated with the Jhala Rajput dynasty.
  • 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_69d6aae5ac3c81908d2b0a3a665665b2 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8904c51b881909e7be84c6f3de79f completed April 10, 2026, 5:53 a.m.
NED1 Entity disambiguation (via context triple) batch_69e7141b16d8819099002a009260a85a completed April 21, 2026, 6:07 a.m.
Created at: April 8, 2026, 9:38 p.m.