Triple

T11443013
Position Surface form Disambiguated ID Type / Status
Subject Yeysk Airport E271191 entity
Predicate hasICAOCode P419 FINISHED
Object URKE
URKE is the ICAO airport code assigned to Yeysk Airport in Russia.
 E926232 NE FINISHED

How this triple was built (4 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: URKE | Statement: [Yeysk Airport, hasICAOCode, URKE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: URKE
Context triple: [Yeysk Airport, hasICAOCode, URKE]
  • A. Urke
    Urke is a small village in Norway situated along the scenic Hjørundfjord, known for its dramatic mountain surroundings and fjord landscapes.
  • B. URU
    URU is the FIFA country code used to represent the Uruguay national football team in international competitions and rankings.
  • C. Urk
    Urk is a traditional Dutch fishing town and former island in the IJsselmeer, now a municipality in the province of Flevoland in the Netherlands.
  • D. Unrug
    Unrug is a Polish noble surname most notably associated with Józef Unrug, a distinguished Polish Navy admiral and World War II commander.
  • E. Usk
    Usk is a small historic town in Monmouthshire, southeast Wales, known for its medieval castle and picturesque setting on the River Usk.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: URKE
Triple: [Yeysk Airport, hasICAOCode, URKE]
Generated description
URKE is the ICAO airport code assigned to Yeysk Airport in Russia.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: URKE
Target entity description: URKE is the ICAO airport code assigned to Yeysk Airport in Russia.
  • A. Urke
    Urke is a small village in Norway situated along the scenic Hjørundfjord, known for its dramatic mountain surroundings and fjord landscapes.
  • B. URU
    URU is the FIFA country code used to represent the Uruguay national football team in international competitions and rankings.
  • C. Urk
    Urk is a traditional Dutch fishing town and former island in the IJsselmeer, now a municipality in the province of Flevoland in the Netherlands.
  • D. Unrug
    Unrug is a Polish noble surname most notably associated with Józef Unrug, a distinguished Polish Navy admiral and World War II commander.
  • E. Usk
    Usk is a small historic town in Monmouthshire, southeast Wales, known for its medieval castle and picturesque setting on the River Usk.
  • F. None of above. chosen

Provenance (5 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_69d6aadff8888190a13f253f0d460874 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d808891b7481908bf5a80cb7644061 completed April 9, 2026, 8:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5d3a2a68481909704ef9a7f780afc completed April 20, 2026, 7:20 a.m.
NEDg Description generation batch_69e5d6a10c0c8190a96a4fc4ef330e8b completed April 20, 2026, 7:32 a.m.
NED2 Entity disambiguation (via description) batch_69e5d7fd235081909870476cbc9817b2 completed April 20, 2026, 7:38 a.m.
Created at: April 8, 2026, 9:35 p.m.