Triple
T1187701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecuadorian sucre |
E25284
|
entity |
| Predicate | hadFrequentDevaluationsIn |
P8578
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Ecuadorian sucre, hadFrequentDevaluationsIn, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadFrequentDevaluationsIn Context triple: [Ecuadorian sucre, hadFrequentDevaluationsIn, 1990s]
-
A.
wasDevaluedIn
chosen
Indicates that the value or worth of an entity was reduced during a specified event, time period, or context.
-
B.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
-
C.
capitalControlsImposed
Indicates that restrictions or regulations have been put in place to limit or manage the flow of capital or financial transactions across borders.
-
D.
formerCurrencyUnion
Indicates that two or more entities were once part of the same currency union, but that monetary union has since been dissolved.
-
E.
usesExchangeRateRegime
Indicates that one entity adopts or operates under a particular exchange rate regime in conducting its currency or monetary arrangements.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd568cf481908d10cf19a3ce28f3 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.