Triple
T15612304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manyara Region |
E375327
|
entity |
| Predicate | regionalCapital |
P3877
|
FINISHED |
| Object | Babati |
E1166041
|
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: Babati | Statement: [Manyara Region, regionalCapital, Babati]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Babati Context triple: [Manyara Region, regionalCapital, Babati]
-
A.
Babati
chosen
Babati is a town in northern Tanzania that serves as an administrative and commercial hub near Lake Babati and the Tarangire National Park.
-
B.
Omuta
Omuta is an industrial city in southern Fukuoka Prefecture, Japan, historically known for its coal mining and chemical industries.
-
C.
Likasi
Likasi is a mining city in the southeastern Democratic Republic of the Congo, known for its significant copper and cobalt production.
-
D.
Mandera
Mandera is a remote town in northeastern Kenya near the borders with Somalia and Ethiopia, serving as a key regional trading and administrative center.
-
E.
Nyamwezi
Nyamwezi is a Bantu language spoken primarily in northwestern Tanzania by the Nyamwezi people.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e8148a0819087d6d69cc84487ca |
completed | April 16, 2026, 2:50 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff5f3913908190acdd7da62b4f521d |
completed | May 9, 2026, 4:22 p.m. |
Created at: April 10, 2026, 4:13 a.m.