Triple
T31877165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HKKI |
E813773
|
entity |
| Predicate | servesProvinceLevel |
P23653
|
FINISHED |
| Object | former Nyanza Province |
—
|
LITERAL 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: former Nyanza Province | Statement: [HKKI, servesProvinceLevel, former Nyanza Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesProvinceLevel Context triple: [HKKI, servesProvinceLevel, former Nyanza Province]
-
A.
servesProvince
Indicates that one entity (typically an organization, service, or administrative unit) provides service or has jurisdiction over a specified province.
-
B.
servedProvince
chosen
Indicates that an entity has provided services or held jurisdictional authority over a specified province.
-
C.
hasProvinceLevelUnit
Indicates that one administrative or territorial entity possesses or contains a sub-unit at the province (or equivalent) level.
-
D.
servesProvinceCapital
Indicates that a city functions as the administrative or service center for a given province’s capital.
-
E.
isProvincial
Indicates that something belongs to, is characteristic of, or is administered at the level of a province rather than a national or local level.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: April 30, 2026, 11:55 p.m.