Triple

T14098101
Position Surface form Disambiguated ID Type / Status
Subject Sofala Province E339307 entity
Predicate hasCapital P204 FINISHED
Object 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: Beira | Statement: [Sofala Province, hasCapital, Beira]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beira
Context triple: [Sofala Province, hasCapital, Beira]
  • A. Beira chosen
    Beira is a major port city in central Mozambique, serving as a key commercial and transport hub for the region.
  • B. 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.
  • C. Lourenço Marques
    Lourenço Marques is the former name of Maputo, the capital city and main port of Mozambique.
  • 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. Beira Alta
    Beira Alta is a historical province in north-central Portugal known for its mountainous landscapes, fortified towns, and wine-producing regions.
  • 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_69d81c69b5c8819094aa1abf18302908 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5fb926288190a7f0f50d1d585d76 completed April 14, 2026, 3:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcd0adfc28819097a1bfd56739c286 completed May 7, 2026, 5:49 p.m.
Created at: April 9, 2026, 10:22 p.m.