Triple
T16131632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wellington Airport |
E391412
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | NZWN |
E391412
|
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: NZWN | Statement: [Wellington Airport, ICAO code, NZWN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NZWN Context triple: [Wellington Airport, ICAO code, NZWN]
-
A.
NZWN
chosen
NZWN is the ICAO airport code for Wellington Airport, the main international gateway serving New Zealand’s capital city.
-
B.
CNWNZ
CNWNZ is the UN/LOCODE identifier for the Port of Wenzhou, a commercial seaport in Wenzhou, China.
-
C.
NZ-WGN
NZ-WGN is the regional code for New Zealand’s Wellington Region, which includes areas such as the Kāpiti Coast.
-
D.
NZ Women
NZ Women is the New Zealand women's national cricket team, representing New Zealand in international women's cricket across all formats.
-
E.
ZWN
ZWN is a former currency code used to denote an early version of the Zimbabwean dollar in international financial and foreign exchange contexts.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a02172c8190978f7951ccd80928 |
completed | April 17, 2026, 11:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff7a0ed9c8190a10fa88ee94811cb |
completed | May 10, 2026, 3:12 a.m. |
Created at: April 10, 2026, 5:01 a.m.