Triple

T1158817
Position Surface form Disambiguated ID Type / Status
Subject San Nicolás de Bari E24446 entity
Predicate currency P245 FINISHED
Object Cuban peso E63202 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: Cuban peso | Statement: [San Nicolás de Bari, currency, Cuban peso]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cuban peso
Context triple: [San Nicolás de Bari, currency, Cuban peso]
  • A. Cuban peso chosen
    The Cuban peso is the official monetary unit of Cuba, used primarily for domestic transactions and issued by the Central Bank of Cuba.
  • B. Dominican peso
    The Dominican peso is the official monetary unit of the Dominican Republic, used for all everyday transactions and financial operations in the country.
  • C. Nicaraguan córdoba
    The Nicaraguan córdoba is the official fiat currency of Nicaragua, issued and regulated by the Central Bank of Nicaragua.
  • D. Colombian peso
    The Colombian peso is the official national currency of Colombia, used for all everyday transactions and financial operations throughout the country.
  • E. Venezuelan bolívar
    The Venezuelan bolívar is the official fiat currency of Venezuela, historically affected by high inflation and multiple redenominations.
  • 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_69a494060e148190abb42f971242c197 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bcad47a08190895769611798f67f completed March 1, 2026, 10:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac5ebbf80881909010e1e1e59212d4 completed March 7, 2026, 5:22 p.m.
Created at: March 1, 2026, 7:45 p.m.