Triple

T6648910
Position Surface form Disambiguated ID Type / Status
Subject Eusébio E150769 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: [Eusébio, placeOfBirth, Lourenço Marques]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lourenço Marques
Context triple: [Eusébio, 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. Beira (Portugal)
    Beira is a historical region in central Portugal known for its mountainous landscapes, fortified towns, and role as a traditional territorial division of the country.
  • D. Porto dos Casais
    Porto dos Casais was the original colonial settlement that later developed into the Brazilian city of Porto Alegre.
  • E. 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.
  • 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_69c687f1a3048190828b7342f7125d5c completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6b01fea4c8190a21ba7f4c2018c5e completed March 27, 2026, 4:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6eef91eb08190a00ae027c21b08bf completed March 27, 2026, 8:56 p.m.
Created at: March 27, 2026, 2:01 p.m.