Triple
T12354178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgarian currency board |
E294565
|
entity |
| Predicate | initialExchangeRate |
P92667
|
FINISHED |
| Object | 1 DEM = 1000 BGL |
—
|
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 DEM = 1000 BGL | Statement: [Bulgarian currency board, initialExchangeRate, 1 DEM = 1000 BGL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialExchangeRate Context triple: [Bulgarian currency board, initialExchangeRate, 1 DEM = 1000 BGL]
-
A.
referenceForExchangeRates
Indicates that something serves as the authoritative source or benchmark used to determine or look up exchange rates between currencies.
-
B.
fixedExchangeRateToUSD
Indicates that the value of one currency is maintained at a constant, predetermined rate relative to the US dollar.
-
C.
exchangeRateAtDollarization
Indicates the exchange rate that was in effect at the time a currency or economy underwent dollarization.
-
D.
currencyExchangeRate
chosen
Indicates the rate at which one currency can be exchanged for another.
-
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.