Triple
T24819694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mackay Airport |
E621025
|
entity |
| Predicate | airlineDestinationType |
P157746
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [Mackay Airport, airlineDestinationType, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineDestinationType Context triple: [Mackay Airport, airlineDestinationType, regional]
-
A.
airlineDestinationType
chosen
Indicates the type or category of destination (e.g., domestic, international, hub) associated with an airline’s route or flight.
-
B.
typicalDestinationAirportIATA
Indicates the IATA airport code that is typically the destination in this kind of trip or route.
-
C.
servesFlightsTo
Indicates that one transportation provider regularly operates flights to a specified destination location.
-
D.
airlineType
Indicates the classification or category of an airline based on its operational or service characteristics.
-
E.
servesAirportType
Indicates that a transportation service or facility provides service to, or is designated for, a specific type or category of airport.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:04 a.m.