Triple

T22117155
Position Surface form Disambiguated ID Type / Status
Subject Island of Mozambique E546572 entity
Predicate replacedAsCapitalBy P3417 FINISHED
Object Lourenço Marques (Maputo) 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: Lourenço Marques (Maputo) | Statement: [Island of Mozambique, replacedAsCapitalBy, Lourenço Marques (Maputo)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lourenço Marques (Maputo)
Context triple: [Island of Mozambique, replacedAsCapitalBy, Lourenço Marques (Maputo)]
  • A. Lourenço Marques chosen
    Lourenço Marques is the former name of Maputo, the capital city and main port of Mozambique.
  • B. Beira
    Beira is a major port city in central Mozambique, serving as a key commercial and transport hub for the region.
  • C. Maputo
    Maputo is the largest city and main economic and cultural center of Mozambique, located on the country’s southern coast along the Indian Ocean.
  • D. Nampula
    Nampula is a major city in northern Mozambique that serves as an important commercial and transportation hub for the region.
  • E. Johannesburg–Maputo
    Johannesburg–Maputo is an international air route linking Johannesburg, South Africa with Maputo, the capital of Mozambique.
  • 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_69e11e38b3848190ac3a4fa97d56e65a completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1294e85708190b455846bacbdfd03 completed April 28, 2026, 9:40 p.m.
Created at: April 16, 2026, 8:31 p.m.