Triple
T4372268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venezuelan bolívar |
E98922
|
entity |
| Predicate | hasCurrencySystemChange |
P8048
|
FINISHED |
| Object | introduction of bolívar fuerte in 2008 |
—
|
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: introduction of bolívar fuerte in 2008 | Statement: [Venezuelan bolívar, hasCurrencySystemChange, introduction of bolívar fuerte in 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrencySystemChange Context triple: [Venezuelan bolívar, hasCurrencySystemChange, introduction of bolívar fuerte in 2008]
-
A.
replacedCurrency
Indicates that one currency has been superseded and no longer used because another currency has taken its place.
-
B.
successorMonetarySystem
chosen
Indicates that one monetary system directly follows and replaces another in time or function.
-
C.
monetarySystemType
Indicates the type or classification of a monetary system associated with an entity.
-
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.
coexistedWithCurrency
Indicates that one currency was in circulation at the same time as another currency.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3521dffbc8190b9300a7f4f64bdc0 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:17 p.m.