Triple
T13811084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puerto Plata |
E331889
|
entity |
| Predicate | currency |
P245
|
FINISHED |
| Object | Dominican peso |
E101646
|
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: Dominican peso | Statement: [Puerto Plata, currency, Dominican peso]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dominican peso Context triple: [Puerto Plata, currency, Dominican peso]
-
A.
Dominican peso
chosen
The Dominican peso is the official monetary unit of the Dominican Republic, used for all everyday transactions and financial operations in the country.
-
B.
Nicaraguan córdoba
The Nicaraguan córdoba is the official fiat currency of Nicaragua, issued and regulated by the Central Bank of Nicaragua.
-
C.
Cuban peso
The Cuban peso is the official monetary unit of Cuba, used primarily for domestic transactions and issued by the Central Bank of Cuba.
-
D.
Costa Rican peso
The Costa Rican peso was the former official currency of Costa Rica before it was succeeded by the Costa Rican colón.
-
E.
Colombian escudo
The Colombian escudo was a historical currency of Colombia used primarily during the colonial and early republican periods before being replaced by the Colombian peso.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026ff6b481908066d6bf27064417 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b09161108190abbd97a30af9ab49 |
completed | May 3, 2026, 8:31 p.m. |
Created at: April 9, 2026, 10:12 p.m.