Triple
T28361255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenya (former provinces system) |
E718367
|
entity |
| Predicate | capitalOfEasternProvince |
P175649
|
FINISHED |
| Object | Embu |
—
|
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: Embu | Statement: [Kenya (former provinces system), capitalOfEasternProvince, Embu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfEasternProvince Context triple: [Kenya (former provinces system), capitalOfEasternProvince, Embu]
-
A.
capitalOfSeniorateProvince
Indicates that a city serves as the capital of a specified seniorate province within a political or administrative system.
-
B.
capitalOfSubregionLocatedHere
Indicates that a place serves as the capital of a subregion that is geographically located within it.
-
C.
capitalOfProvinceCaptured
Indicates that a particular force or entity has taken control of the capital city of a specified province.
-
D.
ancientCapitalLocatedIn
Indicates that a city served as the capital of an ancient polity or civilization and was geographically situated within a specified region or territory.
-
E.
romanProvinceCapital
Indicates that one place served as the administrative capital of a specified Roman province.
- F. None of above. chosen
Provenance (4 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_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: April 28, 2026, 12:52 a.m.