Triple
T11870925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tainan Airport |
E282403
|
entity |
| Predicate | hasCode |
P9567
|
FINISHED |
| Object | TNN |
E951131
|
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: TNN | Statement: [Tainan Airport, hasCode, TNN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TNN Context triple: [Tainan Airport, hasCode, TNN]
-
A.
TNN
TNN, originally known as The Nashville Network, was a U.S. cable television channel that evolved from country-music-focused programming into a broader general entertainment network before rebranding as Spike.
-
B.
TNN
chosen
TNN is the IATA airport code for Tainan Airport, a regional airport serving the city of Tainan in southern Taiwan.
-
C.
TN
TN is the official two-letter U.S. Postal Service abbreviation for the state of Tennessee.
-
D.
TN
TN is the official vehicle registration code used for the Indian state of Tamil Nadu.
-
E.
TN
TN is a UK postcode area covering Tunbridge Wells and surrounding parts of Kent and East Sussex.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8be15fb2481908f514781ce2c617f |
completed | April 10, 2026, 9:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f417bb131c8190b0923e077cca74be |
completed | May 1, 2026, 3:02 a.m. |
Created at: April 8, 2026, 9:43 p.m.