Triple

T28525992
Position Surface form Disambiguated ID Type / Status
Subject Kirinyaga County E721904 entity
Predicate hasConstituency P1971 FINISHED
Object Mwea Constituency
Mwea Constituency is an electoral constituency in Kenya located within Kirinyaga County, known largely for its extensive rice irrigation schemes and agricultural activity.
E1831156 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: Mwea Constituency | Statement: [Kirinyaga County, hasConstituency, Mwea Constituency]
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: Mwea Constituency
Triple: [Kirinyaga County, hasConstituency, Mwea Constituency]
Generated description
Mwea Constituency is an electoral constituency in Kenya located within Kirinyaga County, known largely for its extensive rice irrigation schemes and agricultural activity.

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_69f01a5cbcc4819083fb4e723378713e completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f64fa5ea0c819086708d4430a90a54 completed May 2, 2026, 7:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1ccf2a63548190874c10dd5131a366 completed June 1, 2026, 12:15 a.m.
NEDg Description generation batch_6a1cd020780c81908d33cd9d1676a762 completed June 1, 2026, 12:19 a.m.
NED2 Entity disambiguation (via description) batch_6a24946ccd908190ae144fbc7010aca9 completed June 6, 2026, 9:43 p.m.
Created at: April 28, 2026, 3:24 a.m.