Triple
T10247707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFA franc |
E240259
|
entity |
| Predicate | exchangeRateFixed |
P92667
|
FINISHED |
| Object | 655.957 CFA francs per euro |
—
|
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: 655.957 CFA francs per euro | Statement: [CFA franc, exchangeRateFixed, 655.957 CFA francs per euro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeRateFixed Context triple: [CFA franc, exchangeRateFixed, 655.957 CFA francs per euro]
-
A.
exchangeRateFixingDate
Indicates the specific date on which an exchange rate is determined or fixed for use in a financial transaction or agreement.
-
B.
currencyExchangeRate
chosen
Indicates the rate at which one currency can be exchanged for another.
-
C.
fixedExchangeRateToUSD
Indicates that the value of one currency is maintained at a constant, predetermined rate relative to the US dollar.
-
D.
exchangeCurrency
Indicates a relationship where one party converts or trades an amount of one currency for an equivalent amount of another currency.
-
E.
exchangeRateToPoundSterling
Indicates the rate at which one unit of a given currency can be converted into British pounds sterling.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:27 a.m.