Triple
T30633630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VXP |
E779774
|
entity |
| Predicate | isPrimaryAirportCodeFor |
P115047
|
FINISHED |
| Object | Avelo Airlines |
—
|
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: Avelo Airlines | Statement: [VXP, isPrimaryAirportCodeFor, Avelo Airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryAirportCodeFor Context triple: [VXP, isPrimaryAirportCodeFor, Avelo Airlines]
-
A.
hasPrimaryAirportRole
Indicates that an entity holds the main or principal functional role associated with an airport.
-
B.
operatorPrimaryHubAirportCode
chosen
Indicates the airport code of the main or primary hub used by the operator.
-
C.
isMajorDomesticAirportCode
Indicates that an airport code belongs to a major domestic airport within a given country or region.
-
D.
previousPrimaryAirportFor
Indicates that one airport was formerly the main or primary airport serving a particular location or entity before being replaced by another.
-
E.
servesAsPrimaryAirportOperatorForCity
Indicates that an entity functions as the main organization responsible for operating the primary airport serving a particular city.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 29, 2026, 8:28 p.m.