Triple

T12722340
Position Surface form Disambiguated ID Type / Status
Subject Ramenskoye airfield E304016 entity
Predicate ICAOcode P419 FINISHED
Object UUBW E61663 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: UUBW | Statement: [Ramenskoye airfield, ICAOcode, UUBW]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: UUBW
Context triple: [Ramenskoye airfield, ICAOcode, UUBW]
  • A. UUBW chosen
    UUBW is the ICAO airport code for Zhukovsky International Airport, a major passenger and cargo airport serving the Moscow region in Russia.
  • B. UwB
    UwB is the commonly used abbreviation for the University of Białystok, a public higher education institution in northeastern Poland.
  • C. UbU
    UbU is the commonly used abbreviation for the Swedish Riksdag’s Committee on Education, which handles national education and research policy matters.
  • D. UBN
    UBN is the IATA airport code for the new Chinggis Khaan International Airport serving Ulaanbaatar, Mongolia.
  • E. UUWW
    UUWW is the ICAO airport code assigned to Vnukovo International Airport in Moscow, Russia.
  • 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_69d7bdf084148190ab9d513dc0735af4 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d964133fe481909a44b8159ab8997b completed April 10, 2026, 8:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69f67c841edc81909147d30c51471c47 completed May 2, 2026, 10:36 p.m.
Created at: April 9, 2026, 5:24 p.m.