Triple
T648477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenya |
E11292
|
entity |
| Predicate | majorCity |
P316
|
FINISHED |
| Object | Kisumu |
E43852
|
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: Kisumu | Statement: [Kenya, majorCity, Kisumu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kisumu Context triple: [Kenya, majorCity, 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.
Kigoma
Kigoma is a port city in western Tanzania located on the eastern shore of Lake Tanganyika and serving as a key regional transport and trade hub.
-
C.
Mombasa
Mombasa is a major coastal city in Kenya known as a key regional port and historic trading hub on the Indian Ocean.
-
D.
Uvinza
Uvinza is a town in western Tanzania known historically for its salt production and location along the Central Line railway in Kigoma Region.
-
E.
Nairobi
Nairobi is the capital and largest city of Kenya, serving as a major political, economic, and cultural hub in East Africa.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f308f34819094ba28cfc786051e |
completed | March 1, 2026, 8:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a5c38ffa0c8190af0b6a7528b6c059 |
completed | March 2, 2026, 5:06 p.m. |
Created at: March 1, 2026, 7:36 p.m.