Triple
T5585523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estonian kroon |
E146745
|
entity |
| Predicate | fixedExchangeRateToEUR |
P9578
|
FINISHED |
| Object | 1 EUR = 15.6466 EEK |
—
|
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: 1 EUR = 15.6466 EEK | Statement: [Estonian kroon, fixedExchangeRateToEUR, 1 EUR = 15.6466 EEK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fixedExchangeRateToEUR Context triple: [Estonian kroon, fixedExchangeRateToEUR, 1 EUR = 15.6466 EEK]
-
A.
fixedConversionRateToEuro
chosen
Indicates that one currency has a fixed, predetermined exchange rate relative to the euro.
-
B.
fixedExchangeRateToUSD
Indicates that the value of one currency is maintained at a constant, predetermined rate relative to the US dollar.
-
C.
exchangeRateToPoundSterling
Indicates the rate at which one unit of a given currency can be converted into British pounds sterling.
-
D.
exchangeRateToPapiermark
Indicates the conversion rate or value of one currency in terms of the Papiermark.
-
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.
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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020871a3c8190991f291295cadfa5 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.