Triple
T25028282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exchange Stabilization Fund |
E626768
|
entity |
| Predicate | currencyFocus |
P121378
|
FINISHED |
| Object | U.S. dollar |
—
|
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: U.S. dollar | Statement: [Exchange Stabilization Fund, currencyFocus, U.S. dollar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyFocus Context triple: [Exchange Stabilization Fund, currencyFocus, U.S. dollar]
-
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.
currencyOversight
chosen
Indicates that an entity has authority or responsibility to supervise, regulate, or manage the use, issuance, or stability of a currency.
-
C.
currencyManagedWith
Indicates that a currency is administered, controlled, or operated using a specified system, tool, or mechanism.
-
D.
currencyForm
Indicates that one entity is a specific monetary form, denomination, or variant of the currency represented by the other entity.
-
E.
currencyContext
Indicates that a particular monetary value or transaction is expressed, interpreted, or valid within a specified currency framework or setting.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 6:07 a.m.