Triple

T21612428
Position Surface form Disambiguated ID Type / Status
Subject Anglican Church of Kenya E533344 entity
Predicate hasDiocesesIn P1774 FINISHED
Object Kisumu NE NERFINISHED

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: Kisumu | Statement: [Anglican Church of Kenya, hasDiocesesIn, Kisumu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kisumu
Context triple: [Anglican Church of Kenya, hasDiocesesIn, Kisumu]
  • A. Kisumu chosen
    Kisumu is a major Kenyan city on the shores of Lake Victoria, serving as a key commercial and transport hub in western Kenya.
  • B. Kitale
    Kitale is a town in western Kenya that serves as an important agricultural and commercial center near the slopes of Mount Elgon.
  • C. Kabete
    Kabete is a prominent town in Kenya’s Central Region, situated within Kiambu County and known for its agricultural activity and proximity to Nairobi.
  • D. Msambweni
    Msambweni is a coastal town in southeastern Kenya known for its quiet beaches, fishing activities, and role as a local administrative and trading center.
  • E. Isiolo
    Isiolo is a town in central Kenya that serves as a key transport and commercial hub linking the country’s northern regions with the rest of the nation.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c46411108190bba0d4176dffc9f3 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef3ba79424819094e9ee93c4bbcc0b completed April 27, 2026, 10:34 a.m.
Created at: April 16, 2026, 6:33 p.m.