Triple
T27132179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convertibility Plan (Argentina) |
E681588
|
entity |
| Predicate | pegCurrency |
P19139
|
FINISHED |
| Object | United States dollar |
—
|
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: United States dollar | Statement: [Convertibility Plan (Argentina), pegCurrency, United States dollar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pegCurrency Context triple: [Convertibility Plan (Argentina), pegCurrency, United States dollar]
-
A.
pegTargetCurrency
chosen
Indicates that one currency’s value is fixed or tightly linked to the value of a specified target currency.
-
B.
currencyPeg
Indicates that one currency’s value is fixed or tightly linked to the value of another currency or a basket of currencies.
-
C.
currencySignAdopted
Indicates that a particular currency sign has been officially adopted for use with a given currency or monetary system.
-
D.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
E.
currencyDepicted
Indicates that one entity visually represents or shows the image or symbol of a particular currency on it.
- 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_69f6247832a48190b820e8c0c22ff5db |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:05 a.m.