Triple

T996754
Position Surface form Disambiguated ID Type / Status
Subject Cusco E21511 entity
Predicate currency P245 FINISHED
Object Peruvian sol E10998 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: Peruvian sol | Statement: [Cusco, currency, Peruvian sol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Peruvian sol
Context triple: [Cusco, currency, Peruvian sol]
  • A. Peruvian sol chosen
    The Peruvian sol is the official monetary unit of Peru, used for everyday transactions and economic activities throughout the country.
  • B. Chilean peso
    The Chilean peso is the official monetary unit of Chile, used for everyday transactions and financial operations throughout the country.
  • C. Guaranda
    Guaranda is a small Andean city in central Ecuador known for its traditional architecture, indigenous culture, and vibrant Carnival celebrations.
  • 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_69a493c476b48190b41fc5e793171cc6 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b4df6dcc819084a7c0a50637a2c2 completed March 1, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac2593a6588190b52989e9670d84e3 completed March 7, 2026, 1:18 p.m.
Created at: March 1, 2026, 7:41 p.m.