Triple
T17285914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skardu Airport |
E419654
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | OPSD |
E419655
|
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: OPSD | Statement: [Skardu Airport, ICAO code, OPSD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OPSD Context triple: [Skardu Airport, ICAO code, OPSD]
-
A.
OPSD
chosen
OPSD is the ICAO airport code for Skardu Airport, a key domestic and tourism gateway in the Gilgit-Baltistan region of Pakistan.
-
B.
OPSG
OPSG is a U.S. federal grant program that provides funding to state, local, and tribal law enforcement agencies to enhance border security and cooperation along international land and water borders.
-
C.
OPRN
OPRN is the ICAO airport code for Benazir Bhutto International Airport, the former main international airport serving Islamabad, Pakistan.
-
D.
OPSK
OPSK is the ICAO airport code assigned to Sukkur Airport in Pakistan.
-
E.
OPSI
OPSI is a former UK government body responsible for overseeing the re-use and licensing of public sector information and maintaining official publications.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4378024988190aac6aec006f8f7a1 |
completed | April 19, 2026, 2:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0180d29f4881908694f0182930d716 |
completed | May 11, 2026, 7:10 a.m. |
Created at: April 10, 2026, 5:40 a.m.