Triple
T16830695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uruguayan peso |
E409139
|
entity |
| Predicate | revaluationFactor |
P79535
|
FINISHED |
| Object | 1000 to 1 |
—
|
LITERAL 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: 1000 to 1 | Statement: [Uruguayan peso, revaluationFactor, 1000 to 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revaluationFactor Context triple: [Uruguayan peso, revaluationFactor, 1000 to 1]
-
A.
revaluationRatio
chosen
Indicates the proportional change in value between two states or times, typically expressing how much something has been revalued relative to its previous value.
-
B.
revaluationYear
Indicates the year in which the value of something (such as an asset, currency, or property) is reassessed or adjusted.
-
C.
successorCurrencySubunitRatio
Indicates the numerical conversion ratio between the smallest subunit of a successor currency and the subunit of the currency it replaces.
-
D.
replacedCurrency
Indicates that one currency has been superseded and no longer used because another currency has taken its place.
-
E.
replacedCurrencyRate
Indicates that one currency exchange rate has been superseded or substituted by another rate in a given context.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b316acc881909c686add53d72388 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.