Triple

T7911506
Position Surface form Disambiguated ID Type / Status
Subject Mbeya Region E183708 entity
Predicate hasBorderTown P847 FINISHED
Object Tunduma E633689 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: Tunduma | Statement: [Mbeya Region, hasBorderTown, Tunduma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tunduma
Context triple: [Mbeya Region, hasBorderTown, Tunduma]
  • A. Tunduma chosen
    Tunduma is a border town in southern Tanzania that serves as a major road and rail gateway for trade and travel between Tanzania and Zambia.
  • B. Dumenza
    Dumenza is a small municipality in the Lombardy region of northern Italy, located in the Province of Varese near the Swiss border.
  • C. Tantamani
    Tantamani was a Kushite king of the 25th Dynasty of Egypt, known for his brief attempt to restore Nubian control over Egypt before being driven back by the Assyrians.
  • D. Zumwa
    Zumwa is the Gbagyi-language name for Zuma Rock, the iconic monolithic inselberg near Abuja, Nigeria.
  • E. Ndugu
    Ndugu is a surname of likely African origin borne by various individuals, including those with the given name Bailey.
  • 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_69ca828dec0c81908b8f55a4dbbb53ff completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a725b8c8190a530adb3107a95dd completed March 31, 2026, 3:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbdff156c481909a32be8828f407ad completed March 31, 2026, 2:53 p.m.
Created at: March 30, 2026, 5:04 p.m.