Triple
T3612586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kilimanjaro Region |
E76522
|
entity |
| Predicate | largestCity |
P235
|
FINISHED |
| Object | Moshi |
E76525
|
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: Moshi | Statement: [Kilimanjaro Region, largestCity, Moshi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moshi Context triple: [Kilimanjaro Region, largestCity, Moshi]
-
A.
Moshi
chosen
Moshi is a Tanzanian town in the Kilimanjaro Region that serves as a major gateway and base for climbers ascending Mount Kilimanjaro.
-
B.
Zanzibar City
Zanzibar City is the historic and administrative capital of Zanzibar, Tanzania, renowned for its UNESCO-listed Stone Town and rich Swahili, Arab, and colonial heritage.
-
C.
Dar es Salaam
Dar es Salaam is a major coastal metropolis on the Indian Ocean and the principal economic and commercial hub of Tanzania.
-
D.
Mombasa
Mombasa is a major coastal city in Kenya known as a key regional port and historic trading hub on the Indian Ocean.
-
E.
Dodoma
Dodoma is the political and administrative capital city of Tanzania, located in the country’s central region.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc22e5b30819084184b730732c727 |
completed | March 8, 2026, 6:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4882d20fc819082c0b640cddce269 |
completed | March 13, 2026, 9:57 p.m. |
Created at: March 8, 2026, 3:23 p.m.