Triple
T1223848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZWL |
E26282
|
entity |
| Predicate | predecessorCurrencyCode |
P15239
|
FINISHED |
| Object | ZWR |
—
|
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: ZWR | Statement: [ZWL, predecessorCurrencyCode, ZWR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorCurrencyCode Context triple: [ZWL, predecessorCurrencyCode, ZWR]
-
A.
previousCurrency
Indicates that one currency served as the predecessor or was replaced by another currency in a monetary system or sequence.
-
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.
formerISO4217Code
chosen
Indicates that an entity was previously assigned a particular ISO 4217 currency code that is no longer in current use for it.
-
D.
associatedCurrencyCode
Indicates the currency code that is linked to or used in connection with the given entity or transaction.
-
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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be233fd88190996faf4105c0b8d7 |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.