Triple
T11046727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand Order of Merit |
E261154
|
entity |
| Predicate | postNominalForGrade |
P1610
|
FINISHED |
| Object | KNZM |
E850881
|
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: KNZM | Statement: [New Zealand Order of Merit, postNominalForGrade, KNZM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KNZM Context triple: [New Zealand Order of Merit, postNominalForGrade, KNZM]
-
A.
KNZM
chosen
KNZM is the post-nominal title used by individuals appointed as Knights Companion of the New Zealand Order of Merit, one of New Zealand’s principal honours.
-
B.
KZ
KZ is the two-letter ISO 3166-1 alpha-2 country code assigned to Kazakhstan for international standardization and identification.
-
C.
KNO
KNO is the IATA airport code for Kualanamu International Airport serving Medan and the surrounding region in North Sumatra, Indonesia.
-
D.
KZT
KZT is the currency code for the Kazakhstani tenge, the official monetary unit of Kazakhstan.
-
E.
KNF
KNF is the IATA airport code for RAF Marham, a Royal Air Force station in Norfolk, England.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798307da481908996557a73c9b49a |
completed | April 9, 2026, 12:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3a9fad8248190810e097d148655f5 |
completed | April 18, 2026, 3:57 p.m. |
Created at: April 8, 2026, 9:26 p.m.