Triple
T16131631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wellington Airport |
E391412
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | WLG |
E391411
|
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: WLG | Statement: [Wellington Airport, IATA code, WLG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WLG Context triple: [Wellington Airport, IATA code, WLG]
-
A.
WLG
WLG is the National Rail station code for Wallasey Grove Road railway station in Merseyside, England.
-
B.
WLG
chosen
WLG is the three-letter IATA airport code assigned to Wellington Airport, the main international gateway to New Zealand’s capital city.
-
C.
WLD
WLD is the native cryptocurrency token of the Worldcoin project, used for governance, incentives, and participation within its identity and financial ecosystem.
-
D.
BE-WLG
BE-WLG is the ISO 3166-2 code that uniquely identifies the Belgian province of Liège.
-
E.
LWL
LWL is the vehicle registration code assigned to the Włodawa area in eastern Poland.
- 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_69fff2b1b7248190a1bba4a87db8318b |
completed | May 10, 2026, 2:51 a.m. |
Created at: April 10, 2026, 5:01 a.m.