Triple
T35604458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devonport Airport |
E1028845
|
entity |
| Predicate | primaryAirlineType |
P9478
|
FINISHED |
| Object | regional airlines |
—
|
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 airlines | Statement: [Devonport Airport, primaryAirlineType, regional airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAirlineType Context triple: [Devonport Airport, primaryAirlineType, regional airlines]
-
A.
airlineType
Indicates the classification or category of an airline based on its operational or service characteristics.
-
B.
airlineCategory
Indicates the classification or type of an airline within a defined categorization system (e.g., full-service, low-cost, regional).
-
C.
servesAirlineType
chosen
Indicates that a service provider (such as an airport, terminal, or facility) accommodates or operates flights for a specified type or category of airline.
-
D.
designatedAirlineType
Indicates that an airline has been assigned a specific operational or classification type for a given context or service.
-
E.
primaryHubAirline
Indicates that an airline serves as the main or principal hub carrier for a particular airport or location.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.