Triple
T1980022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McGhee Tyson Airport |
E43003
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | TYS |
E221856
|
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: TYS | Statement: [McGhee Tyson Airport, FAAcode, TYS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TYS Context triple: [McGhee Tyson Airport, FAAcode, TYS]
-
A.
TYS
chosen
TYS is the IATA airport code for McGhee Tyson Airport, the primary commercial airport serving Knoxville, Tennessee, and the surrounding region.
-
B.
TS
TS is the Technical Secretariat of the Organisation for the Prohibition of Chemical Weapons, the body responsible for implementing and verifying compliance with the Chemical Weapons Convention.
-
C.
TS
TS is the vehicle registration code used on license plates for the Province of Trieste in northeastern Italy.
-
D.
KTYS
KTYS is the ICAO airport code for McGhee Tyson Airport, the primary commercial airport serving Knoxville, Tennessee.
-
E.
YSB
YSB is the IATA airport code for Greater Sudbury Airport in Ontario, Canada.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb7c87bc081908ed179d1ca94fa3b |
completed | March 7, 2026, 5:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae0ad2a3888190a93e54b53a071afc |
completed | March 8, 2026, 11:48 p.m. |
Created at: March 4, 2026, 7:37 p.m.