Triple
T35099819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harambee Avenue |
E1012978
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Nairobi |
C55813
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: road in Nairobi Context triple: [Harambee Avenue, instanceOf, road in Nairobi]
-
A.
road in Kenya
chosen
A road in Kenya is a transportation route that connects urban and rural areas, facilitating movement of people, goods, and services across the country’s diverse landscapes.
-
B.
road in Uganda
A road in Uganda is a transportation route, ranging from paved highways to unpaved rural tracks, that connects towns, villages, and key economic areas across the country’s diverse landscapes.
-
C.
road in Rio de Janeiro
A road in Rio de Janeiro is a public thoroughfare within the city’s urban or suburban area that facilitates vehicular and pedestrian movement while connecting neighborhoods, landmarks, and infrastructure across Rio’s diverse topography.
-
D.
road in South Africa
A road in South Africa is a constructed transportation route, ranging from national highways to local streets, designed to support vehicular and pedestrian movement while adhering to the country’s specific traffic laws, signage standards, and infrastructural conditions.
-
E.
road in Jakarta
A road in Jakarta is a public transportation corridor within the city’s dense urban network, accommodating mixed traffic—from cars and motorcycles to buses and informal transport—while connecting residential, commercial, and industrial areas amid frequent congestion and diverse street-side activities.
- F. None of above.
Provenance (1 batch)
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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.