Triple
T7410079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenerife South Airport |
E170977
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | TFS |
E170976
|
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: TFS | Statement: [Tenerife South Airport, IATA code, TFS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TFS Context triple: [Tenerife South Airport, IATA code, TFS]
-
A.
TFS
chosen
TFS is the IATA airport code for Tenerife South Airport, a major international gateway to Spain’s Canary Islands.
-
B.
TFS
TFS is the Texas A&M Forest Service, a state agency that manages and protects Texas’s forests and related natural resources.
-
C.
Perforce
Perforce is a centralized version control system widely used in game development and large-scale software projects for its performance and robust asset management.
-
D.
TeamSystem
TeamSystem is an Italian software company specializing in business management and accounting solutions for small and medium-sized enterprises.
-
E.
TeamCity
TeamCity is a commercial continuous integration and build management server developed by JetBrains, used to automate building, testing, and deploying software projects.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f29d77848190a6170eb25483224f |
completed | March 27, 2026, 9:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c81edbbe6481908904d1a1f7cfb20a |
completed | March 28, 2026, 6:32 p.m. |
Created at: March 27, 2026, 3:10 p.m.