Triple

T23090497
Position Surface form Disambiguated ID Type / Status
Subject Anapa Airport E575733 entity
Predicate ICAOcode P419 FINISHED
Object URKA 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: URKA | Statement: [Anapa Airport, ICAOcode, URKA]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: URKA
Context triple: [Anapa Airport, ICAOcode, URKA]
  • A. URU
    URU is the FIFA country code used to represent the Uruguay national football team in international competitions and rankings.
  • B. Urke
    Urke is a small village in Norway situated along the scenic Hjørundfjord, known for its dramatic mountain surroundings and fjord landscapes.
  • C. URKE chosen
    URKE is the ICAO airport code assigned to Yeysk Airport in Russia.
  • D. 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.
  • E. Urakhi
    Urakhi is a dialect of the Dargin language spoken by a subset of the Dargin people in the North Caucasus region of Russia.
  • 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_69f18da99bec81908ecadf8dab10d1b7 completed April 29, 2026, 4:48 a.m.
Created at: April 17, 2026, 3:57 p.m.