Triple
T27132180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convertibility Plan (Argentina) |
E681588
|
entity |
| Predicate | domesticCurrency |
P78277
|
FINISHED |
| Object | Argentine peso |
—
|
NE NERFINISHED |
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: Argentine peso | Statement: [Convertibility Plan (Argentina), domesticCurrency, Argentine peso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticCurrency Context triple: [Convertibility Plan (Argentina), domesticCurrency, Argentine peso]
-
A.
localCurrency
chosen
Indicates that a particular currency is officially used or recognized as the standard medium of exchange within a specific locality, region, or country.
-
B.
currencyCountry
Indicates that a given currency is officially used as legal tender in a particular country.
-
C.
currencyFamily
Indicates that two currencies belong to the same broader monetary family or classification, typically sharing a common origin, standard, or structural framework.
-
D.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
E.
currencyNameLocal
Indicates the name of a currency as expressed in the local or native language of the region where it is used.
- F. None of above.
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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 9:05 a.m.