Triple

T30402109
Position Surface form Disambiguated ID Type / Status
Subject Kiserian E773376 entity
Predicate locatedInOrNextToBodyOfWater P1489 FINISHED
Object Kiserian River
Kiserian River is a watercourse in Kenya that flows through the town of Kiserian and supports local agriculture and settlements in the surrounding region.
E2295914 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: Kiserian River | Statement: [Kiserian, locatedInOrNextToBodyOfWater, Kiserian River]
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: Kiserian River
Triple: [Kiserian, locatedInOrNextToBodyOfWater, Kiserian River]
Generated description
Kiserian River is a watercourse in Kenya that flows through the town of Kiserian and supports local agriculture and settlements in the surrounding region.

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_69f2248facd48190b183c3f3ca6daef7 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f68619900c8190b8fcaaeb0c936da9 completed May 2, 2026, 11:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a820ded1ff08190af9511b1499dc32c completed Aug. 16, 2026, 7:22 p.m.
NEDg Description generation batch_6a820e6b44648190bba113cd552a6fda completed Aug. 16, 2026, 7:24 p.m.
NED2 Entity disambiguation (via description) batch_6a820ebe047881909b39fd83f9af05ef completed Aug. 16, 2026, 7:25 p.m.
Created at: April 29, 2026, 8:03 p.m.