Triple
T15023828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sukkur Airport |
E378155
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | SKZ |
E378155
|
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: SKZ | Statement: [Sukkur Airport, IATA code, SKZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SKZ Context triple: [Sukkur Airport, IATA code, SKZ]
-
A.
SKZ
chosen
SKZ is the IATA airport code for Sukkur Airport, which serves the city of Sukkur in Pakistan.
-
B.
SK
SK is the vehicle registration code used on license plates for vehicles registered in Skopje, the capital city of North Macedonia.
-
C.
SK
SK is the postcode area covering Stockport and surrounding parts of Greater Manchester and nearby counties in North West England.
-
D.
SK
SK is the ISO 3166-1 alpha-2 country code for Slovakia, a landlocked Central European nation known for its mountains, castles, and membership in the European Union.
-
E.
SK
SK is the official vehicle registration code assigned to the Indian state of Sikkim.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7de117c8190a1b9fa8d1602057e |
completed | April 15, 2026, 12:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fea5b0bbf4819082e14715bfd6003d |
completed | May 9, 2026, 3:10 a.m. |
Created at: April 10, 2026, 2:56 a.m.