Triple
T16031358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupelo Regional Airport |
E388852
|
entity |
| Predicate | hasFAAIdentifier |
P420
|
FINISHED |
| Object | TUP |
E1188905
|
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: TUP | Statement: [Tupelo Regional Airport, hasFAAIdentifier, TUP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TUP Context triple: [Tupelo Regional Airport, hasFAAIdentifier, TUP]
-
A.
TUP
chosen
TUP is the IATA airport code for Tupelo Regional Airport in Tupelo, Mississippi, United States.
-
B.
Tup
Tup is a town in Kyrgyzstan that serves as one of the main urban centers of the Issyk-Kul Region.
-
C.
TUPJ
TUPJ is the ICAO airport code for Terrance B. Lettsome International Airport, the main air gateway to the British Virgin Islands.
-
D.
Tupe
Tupe is a small Andean town in Peru known for preserving the unique Jaqaru indigenous language and culture.
-
E.
TTPP
TTPP is the ICAO airport code for Piarco International Airport, the main international gateway serving Trinidad and Tobago.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e183384d848190988be7e68770f6ba |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffdbd1cafc81909125174eed475d55 |
completed | May 10, 2026, 1:13 a.m. |
Created at: April 10, 2026, 4:56 a.m.