Triple

T20325372
Position Surface form Disambiguated ID Type / Status
Subject Katanga Province E492318 entity
Predicate containsCity P294 FINISHED
Object Likasi 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: Likasi | Statement: [Katanga Province, containsCity, Likasi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Likasi
Context triple: [Katanga Province, containsCity, Likasi]
  • A. Likasi chosen
    Likasi is a mining city in the southeastern Democratic Republic of the Congo, known for its significant copper and cobalt production.
  • B. Dar es Salaam
    Dar es Salaam is a major coastal metropolis on the Indian Ocean and the principal economic and commercial hub of Tanzania.
  • C. Mikocheni
    Mikocheni is a residential and commercial neighborhood in Dar es Salaam, Tanzania, known for its middle-class housing, offices, and educational institutions.
  • D. Dodoma
    Dodoma is the political and administrative capital city of Tanzania, located in the country’s central region.
  • E. Babati
    Babati is a town in northern Tanzania that serves as an administrative and commercial hub near Lake Babati and the Tarangire National Park.
  • 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_69e0b4a0134081909113563e1c3ba68a completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6778f20288190b1862d6be61bfb67 completed April 20, 2026, 6:59 p.m.
Created at: April 16, 2026, 11:21 a.m.