Triple
T369821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colombian peso |
E8242
|
entity |
| Predicate | currencyType |
P11731
|
FINISHED |
| Object | floating exchange rate |
—
|
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: floating exchange rate | Statement: [Colombian peso, currencyType, floating exchange rate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyType Context triple: [Colombian peso, currencyType, floating exchange rate]
-
A.
currency
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
-
B.
currencyNumber
Indicates the numerical value or denomination associated with a specific currency.
-
C.
currencyNameEnglish
Indicates the English-language name used to refer to a given currency.
-
D.
involvesCurrency
Indicates that the relationship or action includes or pertains to the use, exchange, or specification of a particular currency.
-
E.
codeNumericISO4217
Indicates that an entity is associated with a specific ISO 4217 numeric currency code.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebfdb0608190b1794a871d0d237a |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e960d880819084b3df4e5137a1e2 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0b23ec8190bef9d593162388a4 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.