Triple
T133078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican peso |
E2692
|
entity |
| Predicate | revaluation |
P3714
|
FINISHED |
| Object | 1 new peso (MXN) = 1000 old pesos (MXP) |
—
|
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: 1 new peso (MXN) = 1000 old pesos (MXP) | Statement: [Mexican peso, revaluation, 1 new peso (MXN) = 1000 old pesos (MXP)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revaluation Context triple: [Mexican peso, revaluation, 1 new peso (MXN) = 1000 old pesos (MXP)]
-
A.
convertibility
chosen
Indicates the capacity or possibility for one entity, state, or form to be changed or transformed into another.
-
B.
replacedCurrency
Indicates that one currency has been superseded and no longer used because another currency has taken its place.
-
C.
currency
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
-
D.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
-
E.
previousCurrency
Indicates that one currency served as the predecessor or was replaced by another currency in a monetary system or sequence.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a25855baf48190a1b63f2e5865d957 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2564edb488190974dc00eb9ac37d9 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.