Triple
T16980096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Defence University of Kazakhstan |
E411919
|
entity |
| Predicate | countryISOCode |
P42506
|
FINISHED |
| Object | KZ |
E50522
|
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: KZ | Statement: [National Defence University of Kazakhstan, countryISOCode, KZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KZ Context triple: [National Defence University of Kazakhstan, countryISOCode, KZ]
-
A.
KZ
chosen
KZ is the two-letter ISO 3166-1 alpha-2 country code assigned to Kazakhstan for international standardization and identification.
-
B.
Kz
Kz is the currency symbol for the Angolan kwanza, the official monetary unit of Angola.
-
C.
KZJ
KZJ is the Indian Railways station code for Kazipet Junction, a major railway junction in Telangana, India.
-
D.
KZS
KZS is the Slovenian Basketball Federation, the national governing body responsible for organizing and overseeing basketball activities and competitions in Slovenia.
-
E.
KZT
KZT is the currency code for the Kazakhstani tenge, the official monetary unit of Kazakhstan.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d1866bf48190a0ea15c377bf782c |
completed | April 18, 2026, 6:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d477f7ec81909f1f0243004c9050 |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:32 a.m.