Triple
T21786254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | convertible mark |
E537844
|
entity |
| Predicate | formerPegCurrencyCode |
P145931
|
FINISHED |
| Object | DEM |
—
|
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: DEM | Statement: [convertible mark, formerPegCurrencyCode, DEM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerPegCurrencyCode Context triple: [convertible mark, formerPegCurrencyCode, DEM]
-
A.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
-
B.
previousCurrency
Indicates that one currency served as the predecessor or was replaced by another currency in a monetary system or sequence.
-
C.
formerPointsCurrency
Indicates that a points-based currency previously used in a loyalty or rewards program has been discontinued or replaced.
-
D.
formerISO4217Code
Indicates that an entity was previously assigned a particular ISO 4217 currency code that is no longer in current use for it.
-
E.
currencyPeg
Indicates that one currency’s value is fixed or tightly linked to the value of another currency or a basket of currencies.
- F. None of above. chosen
Provenance (4 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0621b5d6881908b74bc999c94fa3d |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:52 p.m.