Triple
T3962896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belize dollar |
E85944
|
entity |
| Predicate | hasCurrencyCodeAlpha3 |
P34151
|
FINISHED |
| Object | BZD |
—
|
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: BZD | Statement: [Belize dollar, hasCurrencyCodeAlpha3, BZD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrencyCodeAlpha3 Context triple: [Belize dollar, hasCurrencyCodeAlpha3, BZD]
-
A.
hasISO4217ThreeLetterCode
chosen
Indicates that an entity is associated with a specific three-letter currency code defined by the ISO 4217 standard.
-
B.
hasISO3166Alpha3Code
Indicates that an entity is associated with a specific three-letter country code defined by the ISO 3166-1 alpha-3 standard.
-
C.
ISO4217CurrencyCodeIssued
Indicates that a specific ISO 4217 currency code has been officially issued or assigned as a valid currency identifier.
-
D.
ISO4217Section
Indicates that something is associated with, defined in, or categorized under a specific section of the ISO 4217 currency standard.
-
E.
codeNumericISO4217
Indicates that an entity is associated with a specific ISO 4217 numeric currency code.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef8efcf3c81908ccf61d9ce26b0c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:31 p.m.