Triple

T13378047
Position Surface form Disambiguated ID Type / Status
Subject Princess of Beira E319240 entity
Predicate namedAfter P63 FINISHED
Object Beira E443290 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: [Princess of Beira, namedAfter, Beira]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beira
Context triple: [Princess of Beira, namedAfter, Beira]
  • A. Beira
    Beira is a major port city in central Mozambique, serving as a key commercial and transport hub for the region.
  • B. Beira (Portugal) chosen
    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_69d806b886bc8190b676e7768b8e01c5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dadce56c6c8190adf4e19f6d1bc233 completed April 11, 2026, 11:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69f726893a8c8190b26b5f7c7fb96f1f completed May 3, 2026, 10:42 a.m.
Created at: April 9, 2026, 9:33 p.m.