Triple

T18090670
Position Surface form Disambiguated ID Type / Status
Subject Forrest City Municipal Airport E432956 entity
Predicate FAAIdentifier P420 FINISHED
Object FCY 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: FCY | Statement: [Forrest City Municipal Airport, FAAIdentifier, FCY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FCY
Context triple: [Forrest City Municipal Airport, FAAIdentifier, FCY]
  • A. FCY chosen
    FCY is the three-letter IATA airport code for Forrest City Municipal Airport in Forrest City, Arkansas, United States.
  • B. CFAY
    CFAY is the U.S. Navy’s Fleet Activities Yokosuka, a major naval installation in Japan that serves as the home port for the U.S. Seventh Fleet.
  • C. DCY
    DCY is the station code for Daly City station, a Bay Area Rapid Transit (BART) rail station serving the city of Daly City, California.
  • D. FY
    FY is a UK postcode area covering parts of the Fylde coast in Lancashire, including towns such as Blackpool and Thornton-Cleveleys.
  • E. FY
    FY is the IATA airline code for Firefly, a Malaysian regional airline operating short-haul flights primarily within Southeast Asia.
  • 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_69d8b907d05c819083cc3bd6021089e6 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4dd17ba98819085a15e8593d98259 completed April 19, 2026, 1:48 p.m.
Created at: April 10, 2026, 10:27 a.m.