Triple
T14589941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andijan Airport |
E342416
|
entity |
| Predicate | icaoCode |
P419
|
FINISHED |
| Object | UTFA |
E1109232
|
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: UTFA | Statement: [Andijan Airport, icaoCode, UTFA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: UTFA Context triple: [Andijan Airport, icaoCode, UTFA]
-
A.
UTFA
chosen
UTFA is the ICAO airport code assigned to Andijan Airport in Uzbekistan.
-
B.
UFAC
UFAC is the French abbreviation for Switzerland’s Federal Office of Civil Aviation, the national authority responsible for regulating and overseeing civil aviation in the country.
-
C.
TuAF
TuAF is the commonly used abbreviation for the Turkish Air Force, the aerial warfare branch of Turkey’s armed forces.
-
D.
TUAC
TUAC is an international trade union body that represents organized labor’s interests in policy discussions and consultations with the Organisation for Economic Co-operation and Development (OECD).
-
E.
UNDAF
UNDAF is the strategic planning framework that guides how United Nations agencies coordinate their development assistance in a given country.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4237d88819097f3f9a40f5be152 |
completed | April 14, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fda918542c819099646943be59dd04 |
completed | May 8, 2026, 9:12 a.m. |
Created at: April 10, 2026, 1:24 a.m.