Triple
T16589616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belize dollar |
E403048
|
entity |
| Predicate | fixedRate |
P51967
|
FINISHED |
| Object | 2 BZD = 1 USD |
—
|
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: 2 BZD = 1 USD | Statement: [Belize dollar, fixedRate, 2 BZD = 1 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fixedRate Context triple: [Belize dollar, fixedRate, 2 BZD = 1 USD]
-
A.
baseRate
Indicates the fundamental or standard rate at which something occurs or is charged, serving as a baseline before adjustments or modifiers are applied.
-
B.
termFixedBy
Indicates that a term is determined, constrained, or made unchangeable by another entity or condition.
-
C.
fixedExchangeRateAgreementWith
chosen
Indicates a formal arrangement in which one entity commits to maintaining a fixed or pegged exchange rate between its currency and that of another entity.
-
D.
finType
Indicates that an entity is of a finite type, meaning it has only a finite number of distinct possible values or elements.
-
E.
rate
Indicates the numerical evaluation or assessment assigned by one entity to another based on perceived quality, performance, or value.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3599f3d18819082b3e6eef5506731 |
completed | April 18, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.