Triple

T20534188
Position Surface form Disambiguated ID Type / Status
Subject Pemba E504149 entity
Predicate hasPort P35 FINISHED
Object Pemba Port NE NERFINISHED

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: Pemba Port | Statement: [Pemba, hasPort, Pemba Port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pemba Port
Context triple: [Pemba, hasPort, Pemba Port]
  • A. Port of Pemba chosen
    The Port of Pemba is a key Indian Ocean harbor in northern Mozambique that serves as a strategic logistics and commercial hub, particularly for the region’s offshore gas and maritime trade activities.
  • B. Pemba
    Pemba is a historically significant coastal city on the Swahili Coast, known as a regional hub of trade and Swahili culture along the Indian Ocean.
  • C. Pemba
    Pemba is a town in southern Zambia that serves as a local commercial and administrative center for the surrounding agricultural region.
  • D. Vilankulo
    Vilankulo is a coastal town in southern Mozambique known as the main gateway to the nearby Bazaruto Archipelago and its popular beach and marine tourism.
  • E. Kilwa Masoko Port
    Kilwa Masoko Port is a coastal seaport in southern Tanzania that serves as a key maritime gateway for the Kilwa area and the wider Lindi Region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4b476648190bc6019622ae54d3c completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a06df04081908fa95c6214f06093 completed April 20, 2026, 9:53 p.m.
Created at: April 16, 2026, 11:37 a.m.