Triple
T7066024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuerteventura Airport |
E164352
|
entity |
| Predicate | hasScheduledAirlineService |
P19814
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fuerteventura Airport, hasScheduledAirlineService, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScheduledAirlineService Context triple: [Fuerteventura Airport, hasScheduledAirlineService, true]
-
A.
hasPassengerAirlineService
Indicates that a location or facility is served by scheduled passenger airline flights.
-
B.
hasScheduledFlights
chosen
Indicates that there are one or more flights planned and set to occur between the related entities according to a schedule.
-
C.
servesAirline
Indicates that a transportation facility or location provides service for, or is regularly used by, a specified airline.
-
D.
servesAirlineType
Indicates that a service provider (such as an airport, terminal, or facility) accommodates or operates flights for a specified type or category of airline.
-
E.
hasNoRegularCommercialAirlineService
Indicates that a location or facility is not served by any scheduled, routine commercial airline flights.
- 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_69c688796c148190adb2f1596f595f22 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4a4e7188190aef123ff1a2aa473 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:39 p.m.