Triple

T9749086
Position Surface form Disambiguated ID Type / Status
Subject Greeneville–Greene County Municipal Airport E236392 entity
Predicate FAA LID P420 FINISHED
Object GCY E819023 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: GCY | Statement: [Greeneville–Greene County Municipal Airport, FAA LID, GCY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GCY
Context triple: [Greeneville–Greene County Municipal Airport, FAA LID, GCY]
  • A. GCY chosen
    GCY is the three-letter IATA airport code for Greeneville–Greene County Municipal Airport in Tennessee, United States.
  • B. KGCY
    KGCY is the ICAO airport code for Greeneville–Greene County Municipal Airport, a public airport serving Greeneville in Greene County, Tennessee, United States.
  • C. CYG
    CYG is the abbreviation commonly used for the Commonwealth Youth Games, an international multi-sport event for young athletes from Commonwealth nations.
  • D. GJ-3
    GJ-3 is the regional vehicle registration code assigned to the city of Rajkot in the Indian state of Gujarat.
  • E. GJ-25
    GJ-25 is the vehicle registration code assigned to the Porbandar district in the Indian state of Gujarat.
  • 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_69ca84d4eddc8190996fec1417d2bae8 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9f6a2f8c8190a6f6af6587ee90b8 completed April 1, 2026, 10:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1bcd2e08c8190808b58fdabe0c9d3 completed April 5, 2026, 1:37 a.m.
Created at: March 30, 2026, 8:23 p.m.