Triple
T457315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovak koruna |
E7260
|
entity |
| Predicate | nonCashChangeoverToEuro |
P7630
|
FINISHED |
| Object | 2009-01-01 |
—
|
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: 2009-01-01 | Statement: [Slovak koruna, nonCashChangeoverToEuro, 2009-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonCashChangeoverToEuro Context triple: [Slovak koruna, nonCashChangeoverToEuro, 2009-01-01]
-
A.
nonCashEuroChangeoverDate
chosen
Indicates the date on which the transition to the euro occurred for non-cash transactions (such as accounting and electronic payments).
-
B.
euroChangeoverCashDate
Indicates the date on which a country or region officially switched its physical cash currency to the euro.
-
C.
fixedConversionRateToEuro
Indicates that one currency has a fixed, predetermined exchange rate relative to the euro.
-
D.
replacedCurrency
Indicates that one currency has been superseded and no longer used because another currency has taken its place.
-
E.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efa1616481909399f92551a0c9e3 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede614b88190be07425f5535f56d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.