Triple
T23082673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anadyr Ugolny Airport |
E575517
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | UHMA |
—
|
NE NERFINISHED |
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: UHMA | Statement: [Anadyr Ugolny Airport, ICAOcode, UHMA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: UHMA Context triple: [Anadyr Ugolny Airport, ICAOcode, UHMA]
-
A.
UHMA
chosen
UHMA is the ICAO airport code for Ugolny Airport, a regional airport serving the Chukotka Autonomous Okrug in Russia.
-
B.
UHSM
UHSM is the ICAO airport code for Yuzhno-Kurilsk Mendeleyevo Airport, a regional airport serving the Kuril Islands in Russia.
-
C.
HMA
HMA is the IATA airport code for Khanty-Mansiysk Airport, which serves the city of Khanty-Mansiysk in Russia.
-
D.
HMA
HMA is a European network of national medicines regulatory authorities that collaborates to ensure the quality, safety, and efficacy of medicinal products across member states.
-
E.
UHMD
UHMD is the ICAO airport code for Provideniya Bay Airport in Russia’s Chukotka region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da239e48190ad041261c6b510a0 |
completed | April 29, 2026, 4:48 a.m. |
Created at: April 17, 2026, 3:56 p.m.