Triple
T18264959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STN |
E437458
|
entity |
| Predicate | revaluationOccurred |
P114510
|
FINISHED |
| Object | 2018 currency reform |
—
|
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: 2018 currency reform | Statement: [STN, revaluationOccurred, 2018 currency reform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revaluationOccurred Context triple: [STN, revaluationOccurred, 2018 currency reform]
-
A.
revaluationRatio
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
chosen
Indicates the year in which the value of something (such as an asset, currency, or property) is reassessed or adjusted.
-
C.
wasDevaluedIn
Indicates that the value or worth of an entity was reduced during a specified event, time period, or context.
-
D.
exchangeRateRegimeChange
Indicates a change in the type or structure of the exchange rate system governing how one currency’s value is determined relative to others.
-
E.
replacedCurrency
Indicates that one currency has been superseded and no longer used because another currency has taken its 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff79851481909a4bbeb14fb00647 |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.