Triple
T24319608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska SkyWest |
E612921
|
entity |
| Predicate | sellsServiceUnderBrand |
P34842
|
FINISHED |
| Object | Alaska 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: Alaska Airlines | Statement: [Alaska SkyWest, sellsServiceUnderBrand, Alaska Airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sellsServiceUnderBrand Context triple: [Alaska SkyWest, sellsServiceUnderBrand, Alaska Airlines]
-
A.
soldBrand
Indicates that a particular brand is sold or offered for sale by a given seller, store, or outlet.
-
B.
sellsOnBehalfOf
Indicates that one party conducts sales transactions as an agent or representative acting on behalf of another party.
-
C.
soldBrandTo
Indicates that one entity transferred ownership or control of a brand to another entity through a sale.
-
D.
serviceBrand
chosen
Indicates that one entity is the brand under which a particular service is offered or marketed by another entity.
-
E.
hasUnderlyingCompanyBrand
Indicates that one entity is associated with or operates under the corporate brand of another company as its underlying brand.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292aa63fc8190a874367c9010f283 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:48 a.m.