Triple

T22214767
Position Surface form Disambiguated ID Type / Status
Subject Kesbewa Divisional Secretariat E549046 entity
Predicate capital P234 FINISHED
Object Kesbewa 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: Kesbewa | Statement: [Kesbewa Divisional Secretariat, capital, Kesbewa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kesbewa
Context triple: [Kesbewa Divisional Secretariat, capital, Kesbewa]
  • A. Kesbewa chosen
    Kesbewa is a suburban town in Sri Lanka’s Western Province, situated within the greater Colombo metropolitan area.
  • B. Khanke
    Khanke is a village in northern Iraq’s Kurdistan Region, known for hosting large camps for internally displaced Yazidis who fled ISIS violence.
  • C. Kuvinga
    Kuvinga is an alternative name for the Kuvi language, a Dravidian language spoken by indigenous communities in eastern India.
  • D. Kwekwe
    Kwekwe is an industrial and mining city in central Zimbabwe known for its steel production and gold mining activities.
  • E. Kukawa
    Kukawa is a historic town in northeastern Nigeria that once served as the political and cultural center of the Kanuri people and the Bornu Empire.
  • 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_69e11e3f7e04819089806d81d5ac431e completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12b8b13f8819099ed8bebbfea3bc8 completed April 28, 2026, 9:50 p.m.
Created at: April 16, 2026, 8:37 p.m.