Triple
T4988625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pevek |
E112070
|
entity |
| Predicate | servedBy |
P82
|
FINISHED |
| Object | Pevek Airport |
E484928
|
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: Pevek Airport | Statement: [Pevek, servedBy, Pevek Airport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pevek Airport Context triple: [Pevek, servedBy, Pevek Airport]
-
A.
Pevek Airport
chosen
Pevek Airport is a small regional airport in Russia’s Chukotka Autonomous Okrug that serves the remote Arctic town of Pevek and its surrounding area.
-
B.
Magadan Airport
Magadan Airport is the main commercial airport serving the city of Magadan in Russia’s Far East, providing regional and limited international air connections.
-
C.
Tunoshna Airport
Tunoshna Airport is a regional airport serving the city of Yaroslavl in Russia, handling both domestic passenger flights and cargo operations.
-
D.
Yeysk Airport
Yeysk Airport is a regional airport serving the town of Yeysk in Krasnodar Krai, Russia, handling civilian and possibly military aviation operations.
-
E.
Salekhard Airport
Salekhard Airport is a regional airport in northern Russia serving the city of Salekhard and acting as a key base for air transport across the Yamal-Nenets Autonomous Okrug.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd727eae1c819085e5548faadbd162 |
completed | March 20, 2026, 4:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be92521bcc8190a1c485216f885778 |
completed | March 21, 2026, 12:42 p.m. |
Created at: March 20, 2026, 1:34 p.m.