Triple
T30259380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limuru |
E769444
|
entity |
| Predicate | administrativeCountyCapital |
P117280
|
FINISHED |
| Object | Limuru Sub-County |
—
|
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: Limuru Sub-County | Statement: [Limuru, administrativeCountyCapital, Limuru Sub-County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeCountyCapital Context triple: [Limuru, administrativeCountyCapital, Limuru Sub-County]
-
A.
capitalCityOfStateLocatedIn
Indicates that a city serves as the capital of a state, and that state is located within a specified larger geographic or political region.
-
B.
municipalityCapital
Indicates that one entity serves as the administrative capital or seat of government for a given municipality.
-
C.
hasCountyCapitalRole
chosen
Indicates that an entity serves as the administrative capital of a specified county.
-
D.
capitalCityOfStateInRegion
Indicates that a city serves as the capital of a state that is located within a specified region.
-
E.
capitalCityOfJurisdiction
Indicates that one entity is the primary city serving as the official capital of the specified jurisdiction or governing 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 29, 2026, 7:41 p.m.