Triple
T12354182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgarian currency board |
E294565
|
entity |
| Predicate | euroFixingRate |
P9578
|
FINISHED |
| Object | 1 EUR = 1.95583 BGN |
—
|
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 = 1.95583 BGN | Statement: [Bulgarian currency board, euroFixingRate, 1 EUR = 1.95583 BGN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: euroFixingRate Context triple: [Bulgarian currency board, euroFixingRate, 1 EUR = 1.95583 BGN]
-
A.
exchangeRateFixingDate
Indicates the specific date on which an exchange rate is determined or fixed for use in a financial transaction or agreement.
-
B.
exchangeRateToPapiermark
Indicates the conversion rate or value of one currency in terms of the Papiermark.
-
C.
fixedExchangeRateToDEM
Indicates that the value of one currency is pegged at a fixed exchange rate relative to the German Deutsche Mark (DEM).
-
D.
fixedConversionRateToEuro
chosen
Indicates that one currency has a fixed, predetermined exchange rate relative to the euro.
-
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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f8bc60c8190b0ceb84093e70db4 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.