Triple
T15897659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Worth Meacham International Airport |
E385502
|
entity |
| Predicate | hasCode |
P9567
|
FINISHED |
| Object | KFTW |
E385502
|
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: KFTW | Statement: [Fort Worth Meacham International Airport, hasCode, KFTW]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KFTW Context triple: [Fort Worth Meacham International Airport, hasCode, KFTW]
-
A.
KFTW
chosen
KFTW is the ICAO airport code for Fort Worth Meacham International Airport, a general aviation and reliever airport serving the Fort Worth, Texas area.
-
B.
KFT
KFT is the commonly used abbreviation for KF Tirana, a prominent Albanian professional football club based in Tirana.
-
C.
KFT
KFT is the former stock ticker symbol for Kraft Foods, a major American food and beverage company known for brands like Kraft cheese, Oreo, and Maxwell House.
-
D.
KTW
KTW is the IATA airport code for Katowice International Airport serving the Silesian region of southern Poland.
-
E.
KTWF
KTWF is the ICAO airport code for Magic Valley Regional Airport serving the Twin Falls area in Idaho, United States.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1563b0e4c8190b338672dfb122665 |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb04d4d1c819091d9b3357ca0deca |
completed | May 9, 2026, 10:08 p.m. |
Created at: April 10, 2026, 4:51 a.m.