Triple

T17703876
Position Surface form Disambiguated ID Type / Status
Subject Central Interior of British Columbia E441378 entity
Predicate hasTown P847 FINISHED
Object Kitwanga E1256394 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: Kitwanga | Statement: [Central Interior of British Columbia, hasTown, Kitwanga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kitwanga
Context triple: [Central Interior of British Columbia, hasTown, Kitwanga]
  • A. Kitwanga chosen
    Kitwanga is a small Gitxsan community in northwestern British Columbia, Canada, known for its rich Indigenous culture and historic totem poles.
  • B. Oshikwambi
    Oshikwambi is a regional dialect of the Oshiwambo language spoken by the Kwambi people in northern Namibia.
  • C. Karonga
    Karonga is a town in northern Malawi located on the shores of Lake Malawi, known as a regional transport hub and archaeological site.
  • D. Kitengela
    Kitengela is a rapidly growing commuter town in Kenya known for its residential estates, industrial development, and proximity to Nairobi.
  • E. Kalungu
    Kalungu is a district in central Uganda that forms part of the traditional Buganda Kingdom region.
  • 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_69d8b9ea20b48190ace88bb46b01e6a9 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e47296770c8190b6b172fb647da564 completed April 19, 2026, 6:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0242ec0b708190add75f3bd08fc446 completed May 11, 2026, 8:58 p.m.
Created at: April 10, 2026, 10:05 a.m.