Triple
T3399090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XCD |
E71603
|
entity |
| Predicate | fixedExchangeRateToUSD |
P49425
|
FINISHED |
| Object | 2.70 |
—
|
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: 2.70 | Statement: [XCD, fixedExchangeRateToUSD, 2.70]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fixedExchangeRateToUSD Context triple: [XCD, fixedExchangeRateToUSD, 2.70]
-
A.
fixedConversionRateToEuro
Indicates that one currency has a fixed, predetermined exchange rate relative to the euro.
-
B.
exchangeRateToPoundSterling
Indicates the rate at which one unit of a given currency can be converted into British pounds sterling.
-
C.
exchangeRateAtDollarization
Indicates the exchange rate that was in effect at the time a currency or economy underwent dollarization.
-
D.
usesExchangeRateRegime
Indicates that one entity adopts or operates under a particular exchange rate regime in conducting its currency or monetary arrangements.
-
E.
referenceForExchangeRates
Indicates that something serves as the authoritative source or benchmark used to determine or look up exchange rates between 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_69ad85aac4808190a092c9cc8911f584 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8c6b2b08190a307e33c74cf21ad |
completed | March 8, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb2e426b88190b82d9830149b142e |
completed | March 8, 2026, 5:33 p.m. |
Created at: March 8, 2026, 3:14 p.m.