Triple
T28361259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenya (former provinces system) |
E718367
|
entity |
| Predicate | capitalOfRiftValleyProvince |
P37327
|
FINISHED |
| Object | Nakuru |
—
|
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: Nakuru | Statement: [Kenya (former provinces system), capitalOfRiftValleyProvince, Nakuru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfRiftValleyProvince Context triple: [Kenya (former provinces system), capitalOfRiftValleyProvince, Nakuru]
-
A.
capitalOfNyanzaProvince
Indicates that one place serves as the administrative capital of Nyanza Province.
-
B.
capitalOfEasternProvince
Indicates that one entity serves as the capital city or administrative center of a specified eastern province.
-
C.
currentCapitalOfSouthSudan
Indicates that the subject is the city that currently serves as the capital of South Sudan.
-
D.
regionalOrganizationCapital
Indicates that a city serves as the capital or administrative center of a specified regional organization.
-
E.
capitalLocation
chosen
Indicates the relationship in which a place serves as the capital city or administrative center of a given political or geographic entity.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 12:52 a.m.