Triple

T1946891
Position Surface form Disambiguated ID Type / Status
Subject Sheremetyevo International Airport E42073 entity
Predicate ICAOcode P419 FINISHED
Object UUEE E42073 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: UUEE | Statement: [Sheremetyevo International Airport, ICAOcode, UUEE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: UUEE
Context triple: [Sheremetyevo International Airport, ICAOcode, UUEE]
  • A. UUEE chosen
    UUEE is the ICAO airport code for Sheremetyevo International Airport, one of Moscow’s primary international air hubs in Russia.
  • B. UUDD
    UUDD is the ICAO airport code for Moscow’s Domodedovo International Airport, one of Russia’s major aviation hubs.
  • C. UUWW
    UUWW is the ICAO airport code assigned to Vnukovo International Airport in Moscow, Russia.
  • D. UU
    UU is the common abbreviation for Unitarian Universalism, a liberal religious tradition that emphasizes spiritual freedom, reason, and inclusive community.
  • E. EZE
    EZE is the IATA airport code for Ministro Pistarini International Airport, the main international gateway serving Buenos Aires, Argentina.
  • 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_69a8870e08fc8190a319cbf2600db15f completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb32ebae881908f7541301f0198ae completed March 7, 2026, 5:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae0acad6408190ac31a3f817df1360 completed March 8, 2026, 11:48 p.m.
Created at: March 4, 2026, 7:36 p.m.