Triple

T29635689
Position Surface form Disambiguated ID Type / Status
Subject Maseno E755706 entity
Predicate roadConnection P385 FINISHED
Object Kisumu–Busia road
The Kisumu–Busia road is a major highway in western Kenya that links the lakeside city of Kisumu to the border town of Busia, serving as a key regional transport and trade corridor.
E1894395 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–Busia road | Statement: [Maseno, roadConnection, Kisumu–Busia road]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Kisumu–Busia road
Triple: [Maseno, roadConnection, Kisumu–Busia road]
Generated description
The Kisumu–Busia road is a major highway in western Kenya that links the lakeside city of Kisumu to the border town of Busia, serving as a key regional transport and trade corridor.

Provenance (5 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_69f0ef88fbe081908f0ad90c1c413f1c completed April 28, 2026, 5:34 p.m.
NER Named-entity recognition batch_69f66e6a2790819082fb230e553bf4c5 completed May 2, 2026, 9:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2721d442b0819087f07e25f18a922b completed June 8, 2026, 8:11 p.m.
NEDg Description generation batch_6a2723656f888190b66e470c94c4e03f completed June 8, 2026, 8:17 p.m.
NED2 Entity disambiguation (via description) batch_6a2723e6c6648190801fec9c9fd7f557 completed June 8, 2026, 8:19 p.m.
Created at: April 28, 2026, 6:44 p.m.