Triple
T2184365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Bank of Kazakhstan |
E49116
|
entity |
| Predicate | currencyCode |
P208
|
FINISHED |
| Object | KZT |
E49115
|
NE 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: KZT | Statement: [National Bank of Kazakhstan, currencyCode, KZT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KZT Context triple: [National Bank of Kazakhstan, currencyCode, KZT]
-
A.
KZT
chosen
KZT is the currency code for the Kazakhstani tenge, the official monetary unit of Kazakhstan.
-
B.
KZ
KZ is the two-letter ISO 3166-1 alpha-2 country code assigned to Kazakhstan for international standardization and identification.
-
C.
KAZ
KAZ is the three-letter ISO 3166-1 alpha-3 country code assigned to Kazakhstan for international standardization and identification.
-
D.
Kt
Kt is the post-nominal abbreviation used to denote a Knight Bachelor in the British honours system.
-
E.
KT
KT is a UK postcode area covering Kingston upon Thames and surrounding parts of southwest London and north Surrey.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf0e92248190a9449fce4044438a |
completed | March 7, 2026, 6 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae71b3eed081909a09bf1ef622fad8 |
completed | March 9, 2026, 7:07 a.m. |
Created at: March 4, 2026, 7:45 p.m.