Triple

T16728301
Position Surface form Disambiguated ID Type / Status
Subject Limuru Road E406519 entity
Predicate namedAfter P63 FINISHED
Object Limuru town E769444 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: Limuru town | Statement: [Limuru Road, namedAfter, Limuru town]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Limuru town
Context triple: [Limuru Road, namedAfter, Limuru town]
  • A. Limuru chosen
    Limuru is a highland town in central Kenya known for its cool climate, tea plantations, and proximity to Nairobi.
  • B. Yaunde
    Yaunde is an alternative name for Kolo, likely referring to the same place or entity under a different local or historical designation.
  • C. Tsavo town
    Tsavo town is a small settlement in southeastern Kenya that serves as a gateway to the nearby Tsavo East and Tsavo West National Parks.
  • D. Mogoro
    Mogoro is a small town and municipality in central-western Sardinia, Italy, known for its traditional crafts and wine production.
  • E. Itezhi-Tezhi town
    Itezhi-Tezhi town is a settlement in Zambia that developed near the Itezhi-Tezhi Dam and serves as a local center for services and access to the surrounding rural and wildlife areas.
  • 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_69d8838f242881908abd8bc138795886 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e38749baa48190892b2e2b978f6eb6 completed April 18, 2026, 1:29 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00a519a89081909456bb6fc25d9234 completed May 10, 2026, 3:32 p.m.
Created at: April 10, 2026, 5:20 a.m.