Triple
T33777834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bomet County |
E865568
|
entity |
| Predicate | hasSubCounty |
P747
|
FINISHED |
| Object | Bomet East |
—
|
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: Bomet East | Statement: [Bomet County, hasSubCounty, Bomet East]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubCounty Context triple: [Bomet County, hasSubCounty, Bomet East]
-
A.
hasSubdivision
chosen
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
B.
hasNumberOfSubdistricts
Indicates the relationship specifying how many subdistricts are associated with a given entity.
-
C.
isInCountySubdivision
Indicates that one entity (typically a place or address) is located within the boundaries of a specific county subdivision.
-
D.
hasSuburbanMunicipality
Indicates that one administrative region includes or is associated with a municipality located in a suburban area.
-
E.
hasSubdivisionCode
Indicates that an entity is associated with a specific code identifying one of its internal subdivisions (such as a state, province, or region).
- F. None of above.
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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
Created at: May 1, 2026, 1:45 a.m.