Triple
T7410102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenerife South Airport |
E170977
|
entity |
| Predicate | serves as |
P11687
|
FINISHED |
| Object | major tourist gateway to Tenerife |
—
|
LITERAL 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: major tourist gateway to Tenerife | Statement: [Tenerife South Airport, serves as, major tourist gateway to Tenerife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serves as Context triple: [Tenerife South Airport, serves as, major tourist gateway to Tenerife]
-
A.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
-
B.
servesUse
Indicates that one entity is used by or functions to serve the purpose or needs of another entity.
-
C.
servesRole
chosen
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
D.
servesAsQualifierFor
Indicates that one entity functions as a qualifier or modifier that refines, restricts, or specifies the meaning or scope of another entity.
-
E.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
- F. None of above.
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. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:10 p.m.