Triple
T6907438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenerife North Airport |
E159845
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | TFN |
E159845
|
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: TFN | Statement: [Tenerife North Airport, IATA code, TFN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TFN Context triple: [Tenerife North Airport, IATA code, TFN]
-
A.
TFN
chosen
TFN is the IATA airport code for Tenerife North Airport, a major airport serving the island of Tenerife in Spain’s Canary Islands.
-
B.
TF
TF is the French abbreviation for the Federal Supreme Court of Switzerland, the country’s highest judicial authority.
-
C.
TF
TF is the vehicle registration code used for motor vehicles registered in the Spanish province of Santa Cruz de Tenerife in the Canary Islands.
-
D.
Tfng
Tfng is the ISO 15924 four-letter code assigned to the Tifinagh script used for writing various Berber (Amazigh) languages.
-
E.
.tf
.tf is the country code top-level domain (ccTLD) designated for the French Southern and Antarctic Lands, an overseas territory of France.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9bd7b3c8190842eb83679c322d5 |
completed | March 27, 2026, 7:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c74901aee08190a5e132200fd58c05 |
completed | March 28, 2026, 3:20 a.m. |
Created at: March 27, 2026, 2:25 p.m.