Triple
T2219892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cypriot pound |
E48115
|
entity |
| Predicate | exchangeRateFixingDate |
P37095
|
FINISHED |
| Object | 10 July 2007 |
—
|
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: 10 July 2007 | Statement: [Cypriot pound, exchangeRateFixingDate, 10 July 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeRateFixingDate Context triple: [Cypriot pound, exchangeRateFixingDate, 10 July 2007]
-
A.
replacedCurrencyDate
Indicates the date on which one currency was officially replaced by another.
-
B.
referenceForExchangeRates
Indicates that something serves as the authoritative source or benchmark used to determine or look up exchange rates between currencies.
-
C.
exchangeRateAtDollarization
Indicates the exchange rate that was in effect at the time a currency or economy underwent dollarization.
-
D.
exchangeRateRegimeChange
Indicates a change in the type or structure of the exchange rate system governing how one currency’s value is determined relative to others.
-
E.
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.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc01386588190a9507f2969a201ca |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbfe93d7c81909f1b9c1b1e3c7989 |
completed | March 7, 2026, 6:04 a.m. |
Created at: March 4, 2026, 7:46 p.m.