Triple
T8540881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBO |
E202189
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Embakasi |
E203057
|
NE 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: Embakasi | Statement: [NBO, locatedNear, Embakasi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Embakasi Context triple: [NBO, locatedNear, Embakasi]
-
A.
Embakasi
chosen
Embakasi is a residential and industrial area in Nairobi, Kenya, known for hosting key infrastructure and serving as a major gateway corridor to the city.
-
B.
Kisumu
Kisumu is a major Kenyan city on the shores of Lake Victoria, serving as a key commercial and transport hub in western Kenya.
-
C.
Eldoret
Eldoret is a major town in western Kenya known as an agricultural and commercial hub and as a center for world-class long-distance runners.
-
D.
Kadoma
Kadoma is a city in central Zimbabwe known for its gold mining and agricultural activities.
-
E.
Kadoma
Kadoma is a city in Osaka Prefecture, Japan, known as a residential and commercial suburb within the Osaka metropolitan area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6e10bc081909a7210c577b807fb |
completed | March 31, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce891a1fac8190bcae4063b24c760a |
completed | April 2, 2026, 3:19 p.m. |
Created at: March 30, 2026, 6:18 p.m.