Triple

T7219269
Position Surface form Disambiguated ID Type / Status
Subject German East Africa E150213 entity
Predicate majorCity P316 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: [German East Africa, majorCity, Moshi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moshi
Context triple: [German East Africa, majorCity, 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. Oshakati
    Oshakati is a major northern Namibian town that serves as an important commercial and administrative hub.
  • D. Dar es Salaam
    Dar es Salaam is a major coastal metropolis on the Indian Ocean and the principal economic and commercial hub of Tanzania.
  • E. Malindi
    Malindi is a historic coastal town in southeastern Kenya known for its beaches, Swahili culture, and role as a former trading port on the Indian Ocean.
  • 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_69c687effb44819092b95d07d0368c9f completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6e9b1a7908190bd215ffb84592e32 completed March 27, 2026, 8:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7db092ed481908f478860418eb0bd completed March 28, 2026, 1:43 p.m.
Created at: March 27, 2026, 2:53 p.m.