Triple
T33174417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Gomera–Tenerife North |
E849127
|
entity |
| Predicate | hasICAODestinationCode |
P84797
|
FINISHED |
| Object | GCXO |
—
|
NE NERFINISHED |
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: GCXO | Statement: [La Gomera–Tenerife North, hasICAODestinationCode, GCXO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasICAODestinationCode Context triple: [La Gomera–Tenerife North, hasICAODestinationCode, GCXO]
-
A.
hasICAOSuccessorCode
Indicates that one ICAO airport code has been replaced or superseded by another ICAO airport code.
-
B.
hasDestinationRegion
Indicates that something is directed, sent, or intended to arrive at a particular geographic or logical region as its destination.
-
C.
isDestinationBased
Indicates that something is determined, organized, or classified according to its destination.
-
D.
hasDestinationState
Indicates that an entity is associated with, directed toward, or results in a particular destination state or condition.
-
E.
hasICAOLocationIndicator
chosen
Indicates that an entity is associated with a specific ICAO location indicator code, typically identifying an airport or aerodrome in the ICAO system.
- 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_69f3495d06508190b0b7729982982cea |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:29 a.m.