Triple

T4191873
Position Surface form Disambiguated ID Type / Status
Subject Otelo E89054 entity
Predicate placeOfBirth P1 FINISHED
Object Lourenço Marques E95848 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: Lourenço Marques | Statement: [Otelo, placeOfBirth, Lourenço Marques]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lourenço Marques
Context triple: [Otelo, placeOfBirth, Lourenço Marques]
  • 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. Jaboatão dos Guararapes
    Jaboatão dos Guararapes is a major coastal city in northeastern Brazil known for its historical significance in the Dutch-Portuguese conflicts and its integration into the metropolitan area of Recife.
  • D. Cantanhede
    Cantanhede is a Portuguese municipality in the Centro Region known for its wine production, agricultural activity, and proximity to the Atlantic coast.
  • E. Port of Salvador
    The Port of Salvador is a major Brazilian seaport and cargo hub on the Atlantic coast, serving as a key gateway for trade in northeastern Brazil.
  • 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_69aed9569a4481908b6c1fcec2a11e21 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af034169f88190a8eb170ba6008b79 completed March 9, 2026, 5:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69b58a08bb6881909bdd7643626e1a64 completed March 14, 2026, 4:17 p.m.
Created at: March 9, 2026, 3:46 p.m.