Triple

T13558406
Position Surface form Disambiguated ID Type / Status
Subject Ikale E323839 entity
Predicate ethnonym P4709 FINISHED
Object Ikale E323839 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: Ikale | Statement: [Ikale, ethnonym, Ikale]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ikale
Context triple: [Ikale, ethnonym, Ikale]
  • A. Ikale chosen
    Ikale are a prominent Yoruba sub-group in southwestern Nigeria, primarily inhabiting parts of present-day Ondo State and known for their distinct language dialect and cultural traditions.
  • B. Kalsa
    Kalsa is a historic district of Palermo, Italy, known for its Arab-Norman heritage, medieval streets, and vibrant cultural life.
  • C. Ijoko
    Ijoko is a historically significant Awori settlement in southwestern Nigeria that has grown into an important peri-urban community within the Lagos–Ogun metropolitan area.
  • D. Ibirama
    Ibirama is a municipality in the state of Santa Catarina in southern Brazil, known for its strong German cultural heritage and location in the Itajaí Valley region.
  • E. Arakere
    Arakere is a village in the Indian state of Karnataka known historically as the site of the Battle of Arakere during the Fourth Anglo-Mysore War.
  • 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_69d8076830b48190910a902bae5888e2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaff4223c8190801d153ae8f94c73 completed April 12, 2026, 2:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69f75dab4974819097880ad4d50f1b34 completed May 3, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:47 p.m.