Triple
T282898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israeli new shekel |
E5826
|
entity |
| Predicate | floatingExchangeRate |
P5803
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Israeli new shekel, floatingExchangeRate, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floatingExchangeRate Context triple: [Israeli new shekel, floatingExchangeRate, yes]
-
A.
isFloatingCurrency
chosen
Indicates that a currency’s value is determined by market forces and allowed to fluctuate freely rather than being fixed to another asset or currency.
-
B.
usesExchangeRateRegime
Indicates that one entity adopts or operates under a particular exchange rate regime in conducting its currency or monetary arrangements.
-
C.
exchangeRateRegime
Indicates the type of system or policy a country or authority uses to manage and determine the value of its currency relative to other currencies.
-
D.
involvesCurrency
Indicates that the relationship or action includes or pertains to the use, exchange, or specification of a particular currency.
-
E.
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).
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e0c14b48190a5c936bab36180b3 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b795a6c8190944d48e8418e0ccd |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.