Triple
T33341875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franc Zone |
E853692
|
entity |
| Predicate | usesExchangeRatePeg |
P26645
|
FINISHED |
| Object | euro |
—
|
NE NERFINISHED |
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: euro | Statement: [Franc Zone, usesExchangeRatePeg, euro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesExchangeRatePeg Context triple: [Franc Zone, usesExchangeRatePeg, euro]
-
A.
usesExchangeRateRegime
Indicates that one entity adopts or operates under a particular exchange rate regime in conducting its currency or monetary arrangements.
-
B.
currencyPeg
chosen
Indicates that one currency’s value is fixed or tightly linked to the value of another currency or a basket of currencies.
-
C.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
D.
usesCurrencyInitially
Indicates that an entity originally adopts or operates with a particular currency at the start of a defined period or process.
-
E.
fixedExchangeRateToUSD
Indicates that the value of one currency is maintained at a constant, predetermined rate relative to the US dollar.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.