Triple
T6466065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | peso boliviano |
E142234
|
entity |
| Predicate | monetaryReformYear |
P8045
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [peso boliviano, monetaryReformYear, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monetaryReformYear Context triple: [peso boliviano, monetaryReformYear, 1987]
-
A.
monetaryAuthorityEstablishedYear
Indicates the year in which a given monetary authority was formally established.
-
B.
redenominationDate
Indicates the date on which a currency or financial instrument undergoes a formal change in its nominal value or unit (redenomination).
-
C.
reintroducedCurrencyOf
Indicates that a currency has been brought back into use as legal tender in a particular country or region after having been previously replaced, discontinued, or suspended.
-
D.
firstRedenominationYear
Indicates the year in which a currency or financial unit was first redenominated (i.e., its face value was officially recalibrated or replaced).
-
E.
thirdRedenominationYear
chosen
Indicates the calendar year in which the third redenomination event of a currency or financial instrument took place.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a1159ec81909bbfa9a9d6fa1616 |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:49 p.m.