Triple

T15266400
Position Surface form Disambiguated ID Type / Status
Subject Lagos Mainland E364910 entity
Predicate hasNeighbourhood P4813 FINISHED
Object Jibowu E963371 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: Jibowu | Statement: [Lagos Mainland, hasNeighbourhood, Jibowu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jibowu
Context triple: [Lagos Mainland, hasNeighbourhood, Jibowu]
  • A. Jibowu chosen
    Jibowu is a busy urban district in Lagos, Nigeria, known as a major transport hub with numerous intercity bus terminals and easy access to key city routes.
  • B. Enbo
    Enbo is a given name most notably associated with Tang Enbo, a prominent Chinese Nationalist general during the Second Sino-Japanese War and Chinese Civil War.
  • C. Banzebi
    Banzebi are a subgroup of the Nzebi people, an ethnic community primarily found in Central Africa, especially in Gabon and surrounding regions.
  • D. Jiwere
    Jiwere is the self-designated name of the Otoe people and their language, part of the Siouan language family of Native North America.
  • E. Surobi
    Surobi is a town and district in eastern Afghanistan, strategically located along the Kabul River and a key site for nearby hydroelectric infrastructure.
  • 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_69d85a0f08408190b3c3259ae35d79d2 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e00851c5b88190a296b6a105d3ee30 completed April 15, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69feef6fc290819096ef03f8ecae8876 completed May 9, 2026, 8:25 a.m.
Created at: April 10, 2026, 3:14 a.m.