Triple

T559306
Position Surface form Disambiguated ID Type / Status
Subject Mozambique E13411 entity
Predicate hasImportantPort P6498 FINISHED
Object Port of Beira E66877 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: Port of Beira | Statement: [Mozambique, hasImportantPort, Port of Beira]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Port of Beira
Context triple: [Mozambique, hasImportantPort, Port of Beira]
  • A. Port of Maputo
    The Port of Maputo is Mozambique’s principal deep-water seaport and a major regional hub for maritime trade in southeastern Africa.
  • B. Beira chosen
    Beira is a major port city in central Mozambique, serving as a key commercial and transport hub for the region.
  • C. Port of Muanda
    The Port of Muanda is a coastal seaport in the Democratic Republic of the Congo that serves as a key maritime outlet near the Atlantic terminus of the Congo River.
  • D. Praia
    Praia is the capital and largest city of Cape Verde, located on the southern coast of Santiago Island in the central Atlantic Ocean.
  • E. Port of Ponta Delgada
    The Port of Ponta Delgada is the main commercial and passenger seaport of São Miguel Island, serving as a key maritime gateway for the Azores archipelago in the North Atlantic.
  • 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_69a4933edcf08190b35ecfd6014caee6 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49d28af148190acad3cfb809ff2f2 completed March 1, 2026, 8:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69a4ff488e648190b74d3000e45226b4 completed March 2, 2026, 3:08 a.m.
Created at: March 1, 2026, 7:32 p.m.