Triple

T4858856
Position Surface form Disambiguated ID Type / Status
Subject Texarkana, Arkansas E108604 entity
Predicate airportIATACode P418 FINISHED
Object TXK E450301 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: TXK | Statement: [Texarkana, Arkansas, airportIATACode, TXK]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TXK
Context triple: [Texarkana, Arkansas, airportIATACode, TXK]
  • A. TXK chosen
    TXK is the IATA airport code for Texarkana Regional Airport, which serves the Texarkana area in Texas and Arkansas.
  • B. TXKF
    TXKF is the ICAO airport code for L.F. Wade International Airport, the primary international gateway to Bermuda.
  • C. TXL
    TXL was the IATA airport code for Berlin Tegel Airport, the former main international airport of Berlin, Germany.
  • D. TXN
    TXN is the stock ticker symbol for Texas Instruments Incorporated, a major American technology company known for designing and manufacturing semiconductors and integrated circuits.
  • E. TX-10
    TX-10 is the commonly used abbreviation for Texas's 10th congressional district, a U.S. House of Representatives district covering parts of central Texas.
  • 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_69bd440b965081908b0557721cae6338 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6d5b2f008190a5fd11d3aec165fb completed March 20, 2026, 3:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69be5cf05d7c8190ac6e1b9e93b5256f completed March 21, 2026, 8:55 a.m.
Created at: March 20, 2026, 1:26 p.m.