Triple

T9172934
Position Surface form Disambiguated ID Type / Status
Subject Magic Valley Regional Airport E220123 entity
Predicate FAAcode P420 FINISHED
Object TWF E781662 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: TWF | Statement: [Magic Valley Regional Airport, FAAcode, TWF]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TWF
Context triple: [Magic Valley Regional Airport, FAAcode, TWF]
  • A. TWF chosen
    TWF is the IATA airport code for Magic Valley Regional Airport serving Twin Falls, Idaho, in the United States.
  • B. WBF
    WBF is the German abbreviation for Switzerland’s Federal Department of Economic Affairs, Education and Research, the federal ministry responsible for national economic policy, education, research, and innovation.
  • C. TKF
    TKF is the IATA airport code for Truckee Tahoe Airport, a general aviation airport serving the Truckee and Lake Tahoe region in California, USA.
  • D. FTW
    FTW is the IATA airport code for Fort Worth Meacham International Airport in Fort Worth, Texas.
  • E. FTW
    FTW is the National Rail station code for Fort William railway station in the Scottish Highlands.
  • 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_69ca83e467108190abcae6a33b3d4dad completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccbf9fe79c819082f335c2fdd1c7d3 completed April 1, 2026, 6:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69d05c0a91ec8190a97002660b66aabe completed April 4, 2026, 12:32 a.m.
Created at: March 30, 2026, 7:22 p.m.