Triple
T9500083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VOLARA |
E229112
|
entity |
| Predicate | isLowCostCarrierUnderlying |
P60835
|
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: [VOLARA, isLowCostCarrierUnderlying, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLowCostCarrierUnderlying Context triple: [VOLARA, isLowCostCarrierUnderlying, true]
-
A.
hasLowCostCarrierFocus
Indicates that the subject is primarily oriented toward or strategically focused on serving low-cost carrier operations.
-
B.
hasUnderlyingAirlineCallsign
Indicates that an airline-related entity is associated with a specific underlying airline callsign used for identification in air traffic communications.
-
C.
hasLowCostCarrierOperations
chosen
Indicates that an entity operates or is served by low-cost (budget) airline services.
-
D.
hasUnderlyingCompanyICAOAirlineCode
Indicates that an entity is associated with an underlying company identified by its ICAO airline code.
-
E.
servesAirline
Indicates that a transportation facility or location provides service for, or is regularly used by, a specified airline.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd983c308c8190bde6858ac1ca8ea5 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:56 p.m.