Triple
T10911986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Datooga |
E257722
|
entity |
| Predicate | region |
P40
|
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: [Datooga, region, Dodoma Region]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dodoma Region Context triple: [Datooga, region, 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.
Pwani Region
Pwani Region is a coastal administrative region in eastern Tanzania known for its Swahili culture, Indian Ocean shoreline, and proximity to Dar es Salaam.
-
E.
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.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770723df08190bedfdc94d998f969 |
completed | April 9, 2026, 9:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e155550e388190bd441ac3a9dde435 |
completed | April 16, 2026, 9:32 p.m. |
Created at: April 8, 2026, 9:22 p.m.