Triple

T7994190
Position Surface form Disambiguated ID Type / Status
Subject Singida Region E186081 entity
Predicate borders P224 FINISHED
Object Dodoma Region E472363 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: Dodoma Region | Statement: [Singida Region, borders, Dodoma Region]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dodoma Region
Context triple: [Singida Region, borders, Dodoma Region]
  • A. Dodoma Region chosen
    Dodoma Region is an administrative region in central Tanzania that includes the national capital city, Dodoma.
  • B. Arusha Region
    Arusha Region is an administrative region in northern Tanzania known for its tourism hub city of Arusha and proximity to major national parks and Mount Kilimanjaro.
  • C. Singida Region
    Singida Region is an administrative region in central Tanzania known for its semi-arid climate, agriculture, and role as a transport crossroads.
  • D. Dar es Salaam Region
    Dar es Salaam Region is a coastal administrative region in eastern Tanzania that encompasses the country’s largest city and main economic hub.
  • E. Nyanza region
    Nyanza region is an area in western Kenya along Lake Victoria, known for its predominantly Luo population and the city of Kisumu as its main urban center.
  • 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_69ca829c6c308190ab05b43d234c52b2 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3c73ba388190bcedc29fbdd22f3c completed March 31, 2026, 3:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69cde6dc7b248190b59187a80b4fe036 completed April 2, 2026, 3:47 a.m.
Created at: March 30, 2026, 5:16 p.m.